All posts by Kai Wilzer
When it comes to deployment of asp.net projects there are several ways, as described for example on MSDN. Working with ASP.net for several years I’ve found the easiest way of deployment for myself is using zip / rar to pack an archive of updated files. This works very well in both company and personal webserver […]
One of the important things missing in Microsofts Visual Studio Express Editions is the option to create Unit Tests. Fortunately there are some free Unit Test Tools, like xUnit.net, ExpressUnit, and lots more. Undoubtedly the best-known Unit Test Tool is NUnit. It’s written in C# and works perfect with current .net Frameworks. Setting up the […]
If you haven’t used Sandcastle yet, please have a look at it. It’s easy to create developer documentation with it, especially for dlls you want to share with others. And the comment feature is already included in Visual Studio 2005, so why not use it?
I took over an existing application from an external company. They were not available for us anymore, so we only had the source code on our server. I copied all the c-sharp files and created a new webpage project in my VS 2005. When I built the application it worked fine (after some customization), but […]
Today I wanted to add a new Project to my Team Foundation Server (TFS 2005). Unfortunately it did not work as expected. I entered all the data, and then it stops with error message TF30177: Team Project Creation failed. The details contained some more error codes like TF3004: The New Team Project Wizard encountered an […]
Of course my code uses some dlls. When I’m in debug mode I then get the message “There is no source code available for the current location”. This is ok for most dlls, but if it’s my own dll I have the source code and could select it. Unfortunately it sometimes happens that I click […]
Yes, it’s a long word, but sometimes I got the following error message: Sys.WebForms.PageRequestManagerServerErrorException: An unknown error occured while processing the request on the server. The status code returned from the server was: 500.