Hi!

Today I've tried to build DNN 5.2 in VS 2010 and discovered some erros in ascx files because of new VS 2010 Web Site project Building mode. You can read about the story on MS Connect:

https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=517816

I had to manually correct some ascx files to get things working in VS 2010, and here is my comment about it on Connect:

Hello again folks,

Finally I've built ... DNN 5.2 site in Visual Studio 2010 Beta 2.

First of all, the "Errors referencing Browsers ..." problem is still exists. I had to manually copy *.browser files from .NET FW 2.0 CONFIG folder to DNN App_Browser folder, so I think this is a VS bug. (Big question mark here.)

About other errors: it's not bug, feature. :)

In VS 2010 a Web Site project will fully built before startup even are in IIS. Every directory and every ascx will be processed. And - sadly - some of controls in DNN 5.2 have serious problems:

- You'll get errors about some missing ascx codebehind files. This is because those control are deprecated, not used anywhere - you can delete those ascx files for good.
- You'll get errors about User.ascx described above. This is because of 'style=""width:175px"'. It is not wellformed. You have to replace style="" to style=" in User.ascx.
- You'll get errors about some not wellformed controls in various ascx files because of missing attribute end quotes. You have to fix'em manually. (In about 4-5 ascx.)
- Lastly you'll get an odd VB compiler error about a double reference to System.Web.Extensions.DLL. The problem source lies in DesktopModules\News\RssModule.ascx. It has a Register directive to System.Web.Extensions.DLL. Delete that line for good.

After that you will have a fully working VS 2010 DNN 5.2 solution. Enjoy.

Now I tryin to convert it to .NET 4.0 based website, because I wanna use EF v2 in my new DNN modules and WCF 4 for remode DNN administration. I hope it will possible.

Thanks for this helpful post.

I would never have figured out the copying *.browser files workaround on my own.