Today, I got mad again. These bastards over at Redmond totaly screwed up the deployment and the upgrade mechanisms in Visual Studio 2005. I have a huge project with about 30-40 aspx pages, and I used to have them compiled into one dll with VS 2003. Now, this f*** creates several small App_whatever_hexid.dll-s to make you cry out loud. Of course this breaks the IIS sites sometimes, when you deploy with overwrite - shit happens, dual references.
The best: you can not create a solution. Simply you can't, you can only have several projects (or whatever, because it is now page based) but you can not clearly group in one.
I found an MS WebAPplication Support stuff; but it still does not play as I want. Anyway, at least it will let you create a solution, BUT can not compile and deploy in one step.. so i think i need to write a macro to do this. At least this WAP lets you create a single DLL.
Another madness: the objects created in the aspx file are not referenced in the aspx.cs directly, but they are stored in a separate file with .designer.aspx.cs extension... If you want to add old VS2003 files to a new project, you need to right click and say 'Convert it to a Web Application' - WHY?!
The IDE is the slowest ever. Intelisense is better by no need to type the 'this.' preword to list the local objects.. but fuck, it's 2006, why should I wait seconds to switch between the desing and the code view?!
If you have a Marshalled or InterOped dll, make sure to recompile it, because in 80%, it will not work, and will report funny error codes... who told a thing about framework uncompability issues in *that* low level?!
One positive feeling stuff: VS2005 at least doesn't erase all lines from the InitializeComponent() function when you add events to any object in the Design view, as it was in VS2003 :)

Yes! Microsoft AGAIN did a nice "security enhancement" to make developers nervous. I spent at least two hours to figure out, why my http://projectname.localdomain.tld Web Project is not working in VS.Net 2005 - I couldn't open it as a website, with it's own address, just as a Local Website, and after when I tried to debug it, the IDE replied: logon failure: invalid username or password. The solution is here: You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or IIS 6

1) Grab the packages from http://www.mono-project.com/Downloads 2) Uninstall the packages in this given order: rpm -e mod_mono rpm -e xsp rpm -e mono-data rpm -e bytefx-data-mysql rpm -e mono-winforms rpm -e mono-web rpm -e mono-data rpm -e mono-locale-extras rpm -e mono-core 3) install the same packages in reverse order by calling rpm -i

It's been a long time since I wrote here, well life still goes on - but without any technical problems :) We've started a new project with my new fellows, it's called Webkettő, we're gathering our thoughts on web 2.0 and AJAX (mainly in Hngarian language).

You see the error as well when trying to migrate from a Mono.Net project to an MS.Net project? The key is in the web.config file (one retard thinks he can change everything to make it more 'compatible'): < ?xml version="1.0" encoding="utf-8" ?> <configuration> [...] <system .web> <compilation defaultLanguage="c#" debug="true"> <compilers> <compiler language="cs;c#;csharp" extension=".cs" warningLevel="1" compilerOptions="/codepage:65001" type="Microsoft.CSharp.CSharpCodeProvider, System, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" /> </compilers> [..] </compilation> </system> </configuration> The codepage:utf8 is not valid, it must be a number: 65001. Or you can simply omit this whole line...