Gunnar Peipman's ASP.NET blog
ASP.NET, C#, SharePoint, SQL Server and general software development topics.
-
Refactoring: extract and override factory method
I’m sure you have seen classes that initialize a lot of objects in their constructor. These classes may be hard to test because of those object creations I mentioned. To get around this problem we use Extract and override factory method refactoring so we can extend these classes and override some factory methods.
-
Windows Azure Tools for Microsoft Visual Studio March 2009 CTP
On Friday Microsoft released March 2009 CTP of Windows Azure Tools for Microsoft Visual Studio. You have to remove previous releases of Azure tools before installing new one.
-
Refactoring: adapt parameter
Sometimes you are not able to use Extract Interface refactoring because interface of parameter may be too large or there may be no interface at all. You just have class to pass in and you are not able to fake it or extend it to get class testable. In this case you have to use Adapt Parameter refactoring to create adapter that is seen through common some common class of interface.
-
Windows could not be activated
After installing Windows Server 2008 to one of my development server I got the following error: Windows could not be activated. Exact details of error:
-
SharePoint: Solving the name.dll ActiveX problem – the easy way
It is possible to solve name.dll issue in SharePoint without modifying JavaScript files.
-
Search Engine Optimization: An Hour a Day
-
Solving Azure configuration problems
Putting up development environment for Azure development may be not so smooth and easy task to do. All tools have currently CTP status and it is normal that there may be some problems. Here is my short list of problems. I provide solutions that worked for me. If somebody comes out with different solutions then please feel free to drop me a line.
-
Links 2009-03-13: Article series special
NB! This blog is moved to gunnarpeipman.com
-
SharePoint: Tracing Service lost trace events
Tracing Service lost trace events is one of those nasty entries in ULS log that refers to problems in logger service. If you see messages like these in SharePoint log then simply restart Windows SharePoint Services Tracing service. It took me a while to wonder what is going on until Jim Jackson’s blog entry SharePoint Logs - Tracing Service lost trace events helped me out. Thanks, Jim!
-
Links 2009-03-12
NB! This blog is moved to gunnarpeipman.com