Visual Studio 2005 Web Application Projects - Will DNN adopt? - Extend It! ( Programming in VS2005 & 2008, ASP.Net 2.0 )

Forum General DotNetN... Extend It! ( Pr... Visual Studio 2005 Web Application Projects - Will DNN adopt?

5/10/2006 10:40 AM

	Jeff Martin
61 posts
www.jeffmartin.com

Visual Studio 2005 Web Application Projects - Will DNN adopt?

Modified By Jeff Martin on 5/10/2006 12:43:59 PM)

Microsoft has released Visual Studio 2005 Web Application Projects http://msdn.microsoft.com/asp.net/reference/infrastructure/wap/default.aspx which would seem to make developing modules in DNN much easier - ie... going back to the old way of doing things...having separate projects for modules, etc... not having to worry if you have some extra files under your web directory...

Also check out this blog: http://weblogs.asp.net/scottgu/archive/2006/05/08/445742.aspx

Wish I had seen this coming, we spend ALOT of time migrating our 3 DNN site and project to 4

Jeff Martin
MCSD C#
My Site

5/10/2006 12:06 PM

	Craig Walker
238 posts

Re: Visual Studio 2005 Web Application Projects - Will DNN adopt?

Well I can't speak for DNN as a whole, but as for me and my team, VS2005 Web Apps are the only way to go. I was so disappointed with the "new way", I required my developers to write modules against DNN 3.2 and then install in the production portal running DNN 4. We've been using VS2005 Web Apps since its beta and it makes module development much easier to manage, especially in a multi-developer enviroment. Creating modules as Web Applications eliminates the need to ever open the core project (or touch, or compile, etc) which is my goal from an upgradability standpoint.

5/11/2006 2:16 AM

	Rodney Joyce
1663 posts
www.smart-thinker.com

Re: Visual Studio 2005 Web Application Projects - Will DNN adopt?

I've spent quite a bit of time analysing the new WAP stuff - and I have concluded that it depends on your standpoint.
Basically, because it compiles into one .dll, it's a lot easier for deployment where you don't want to release the source (as opposed to trying to find each .dll per page or folder in the default 2005 method)

For sites where you not concerned about the source being deployed (with compile on demand), then perhaps the old way (!) suits you better.

As a module developer I will be using the WAP architecture - you lose the ability to compile the page only instead of the whole project, but I enjoy the tighter control.

Thanks,
Rodney
Smart-Thinker - Social Networking modules for DotNetNuke
The DotNetNuke Directory - Are you listed?
PokerDIY - Example Implementation of DNN Social Network
Do use DNN a lot? Try the DotNetNuke Toolbar to save you time!

5/11/2006 2:27 AM

	Vladan Strigo
505 posts
Vladan.Strigo.NET

Re: Visual Studio 2005 Web Application Projects - Will DNN adopt?

Well if I recall correctly, Shaun mentioned at sometime that they will not cross to the WAP (pls. correct me if I am wrong on this one....)

But if you want (I plan to try it when I have a few minutes of free time) you can get dnn 4.0.3 and try to convert it.... by the instructions of ScottGu, it should work...

Thanks,
Vladan Strigo
NETMedia

My website: Vladan.Strigo.NET

Vladan.Strigo.NET: Projects
* Advanced VS2005 development approach - BlankModule
* DNN & Microsoft Ajax best practices guidance

Vladan.Strigo.NET: Resources
* Comprehensive list of DNN 4 Module development resources

5/11/2006 4:12 AM

	Sebastian Leupold
15224 posts
www.deutschnetnuke.de

Re: Visual Studio 2005 Web Application Projects - Will DNN adopt?

I expect, that Shaun will blog about this in the near future, please be patient, the Team is currently very busy finishing DNN 3.3.0/4.1.0.

Sebastian Leupold

DotNetNuke Project UserDefinedTable
DotNetNuke Project Release Tracker

Page 1 of 3

Forum

General DotNetN...

Extend It! ( Pr...

Visual Studio 2005 Web Application Projects - Will DNN adopt?