Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Visual Studio 2005 Web Application Projects - Will DNN adopt?Visual Studio 2005 Web Application Projects - Will DNN adopt?
Previous
 
Next
New Post
5/10/2006 12:40 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#
 
New Post
5/10/2006 2:06 PM
 

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.

 
New Post
5/11/2006 4:16 AM
 
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.


Entrepreneur

PokerDIY Tournament Manager - PokerDIY Tournament Manager<
PokerDIY Game Finder - Mobile Apps powered by DNN
PokerDIY - Connecting Poker Players

 
New Post
5/11/2006 4:27 AM
 

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

 
New Post
5/11/2006 6:12 AM
 
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.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Visual Studio 2005 Web Application Projects - Will DNN adopt?Visual Studio 2005 Web Application Projects - Will DNN adopt?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out