Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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.0Using Web Application Projects with DNN 4.xUsing Web Application Projects with DNN 4.x
Previous
 
Next
New Post
6/16/2006 2:38 AM
 
Vladan Strigo

Vladan.Strigo.NET
Joined: 11/27/2003
Posts: 505

Hi Charles,

it's great that you are interested in the idea. You can read more about it by going to my website (link is in my sig) and checking out Bert's ideas also.

My plan is to bring this to a higher level, so any support that the core team can offer us would be great.

 

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
6/16/2006 10:13 AM
 
Bert Corderman

Joined: 5/8/2003
Posts: 109
Vladan Strigo wroteAlso as for MSBuild, I've already made a small MSBuild WDP

IT sounds like you have some of the MSBuild stuff figured out that’s what I was thinking of working together on.  But form your post it appears that you are using a WDP to deploy your code. Why do you need to do this if the WAP project file is an MSBuild file as well?

Vladan Strigo wrote in your approach you hard code the paths to dnn and such. I will continue working on the MSBuild file until I cover most of the basic deployment scenarios (next thing is zipping and packaging, hopefully I can continue on the generic, no hard code streak)


What are you referring to when you are talkign about hard coded paths?  The module project file has a property that tells they module were to build to but this only needs to be changed in once place if you want to move it.

Bert
 
New Post
6/16/2006 10:38 AM
 
Charles Nurse


Charles Nurse's Avatar

Charles Nurse's Avatar

Joined: 2/9/2004
Posts: 3652
Bertcord wrote

My biggest issue with the dynamic approach is there is no way to version your project.  Since all code files are in the same project they all get the same assembly version number.  For custom module developers that need to package and distribute their modules without the source the WAP method is the way to go.  In my opinion anyone that needs this functionality would have a non express version of Visual Studio.



I don't disagree with you Bert.  But, I guess where we were coming from is that most people who are building commercial modules have the skills to create their own development environment.  There are two classes of people who would probably not be as interested in packaging.

1.  Hobby Developers - as I described above.

2. One-off Application Developers - developers building an application (usually as a contractor to or employee of a company), that is a one-off design for a specific need.  These developers are not distributing their code, in fact in most cases, their customer (or employer) owns the code.  These developers are probably more interested in precompiling a site built using the Website Project approach.

Maybe I should ask this question.  Is there a willingness, to work with the core team to make this approach available thru dnn.com?
Charles Nurse
Chief Architect
Evoq Content Team Lead,
DNN Corp.

Want to contribute to the Platform project? - See here 		MVP (ASP.NET) and
ASPInsiders Member
View my profile on LinkedIn
 
New Post
6/16/2006 12:22 PM
 
Bert Corderman

Joined: 5/8/2003
Posts: 109
I agree different people have different needs.  I am also well aware that  DNN must be distributed as a WSP to enable developers with Express the ability to use DNN.  This is why I did not focus on converting the core project.  The benefit of my solution is that it enables module developers to develop modules using WAP WITHOUT changing the core project.

 

cnurse

Maybe I should ask this question.  Is there a willingness, to work with the core team to make this approach available thru dnn.com?

sure, take and use it if you like.  Another interesting point is that even though Express does not support compiling you can still use an MSBuild script to compile code that has been deveolped in Express.  I have a sample of this that I can post if you are interested.

Bert
 
New Post
6/16/2006 12:43 PM
 
brian

Joined: 1/22/2004
Posts: 793

different people have different needs

Unfortunately (change!) or furtunately (better?) MS decided to take a different approach to the process..  not sure exactly why.

Why would a corporate developer (where company owns source) want to open the entire project anyway?  Deploy source, is that how it works?  That is not how development is done..  it is done modular.   What would be the benefit to the dynamic compiling vs WAP..  

I wonder if we have any true .net 2.0 modules developed already or are they simply 1.1 modules tested on dnn 4.x?  

Since we have the ATGen guy on the core team..  and Vincenc (sp?) is also..    why can we not modify those VS temlates, CodeSmith templates or even ATGen templates to use .net 2.0 dnn 4.x ..   or in this case is it too much to modify vs starting over?   That is the ultimate goal I believe..  being able to develop modules quickly using templates.  Blank templates are fine but who really wants that?

(Is DAL+ included in this release..   if not, we need to remember whatever is done now will probably need to be changed again..)

 
 
 Page 11 of 16
Previous123...101112...16Next 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Using Web Application Projects with DNN 4.xUsing Web Application Projects with DNN 4.x


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