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/11/2006 7:43 PM
 
I can't speak for DNN either, but I can tell you that I have successfully converted/created a web application project for Module creation using VS2005; I'm working on making it a project template so that I can create a new Module project without have to include the entire web app. I'm also converting my site, but I'll put it up there (and on my MSDN blog) once I get the time. It also makes it easier to create a PA for deployment of all of the is compiled into a single assembly.
 
New Post
5/12/2006 2:58 AM
 

Actually you don't need DNN core to be WAP - Ill blog about this in a couple of days, it's enough to say for now that DNN and the modules are not even in the same solution (something similar to Speerio MyModules solution) - and it works perfectly, and pretty fast as well - also for the module itself I leverage the WAP so that my .ascx controls can work like they should.

 


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/12/2006 8:24 AM
 
Vladan Strigo wrote

Actually you don't need DNN core to be WAP - Ill blog about this in a couple of days, it's enough to say for now that DNN and the modules are not even in the same solution (something similar to Speerio MyModules solution) - and it works perfectly, and pretty fast as well - also for the module itself I leverage the WAP so that my .ascx controls can work like they should.

 



Got your blog in my RSS reader Vladaan.  Looking forward to it.
 
New Post
5/12/2006 8:26 AM
 
joltcoder wrote
I can't speak for DNN either, but I can tell you that I have successfully converted/created a web application project for Module creation using VS2005; I'm working on making it a project template so that I can create a new Module project without have to include the entire web app. I'm also converting my site, but I'll put it up there (and on my MSDN blog) once I get the time. It also makes it easier to create a PA for deployment of all of the is compiled into a single assembly.


jolt,

I'd llike to give this a try sometime when you have a chance to post it.

-e
 
New Post
5/12/2006 10:14 AM
 

emaynard,

I found some debugging problems with WAP which I'am having with the current setup - as quickly as I resolve them I will post it (decided atleast to post the code until I can write a nice article about it...)

 


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

 
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