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.0DNN4 - Vladan.Strigo.NET or DNN Suggested Dev Environment?DNN4 - Vladan.Strigo.NET or DNN Suggested Dev Environment?
Previous
 
Next
New Post
3/21/2007 4:13 AM
 
wtatters wrote

For closed environment applications - that is - "not planning on a compile any time soon"

 - the asp.net 2.0 route with app_code and friends is a fantastic application enviromment.

The ability to run a LIVE debug - where you are changing code between requests is a HUGE time saver.

Westa

How fast does this work for you? My experience with dynamic compilation and edit & continue with the core approach is that it usually lasts too much time to reload some bits that I could have closed the IE and rebuild my simple solution (with my approach) and opened it all together in that time...(don't confuse this line... just my personal experience)


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
3/21/2007 5:22 AM
 

Umm ok - just a quick timing on the dev box im sitting at:

Assuming that the Webserver and Appliction pool are running - then it takes no longer than about 15 second from hitting the DEBUG button - to a breakpoint set in the PageLoad of a module to trigger.

But what is even better - is that I can change a line of code = or many lines of code.

And hit the Page Refresh  - then it takes about 5 - 8 second for the breakpoint to trigger.

And I can continue to change code on the fly and continue to debug without dropping back to application.

Using your compile - attach - debug method - I would be surprised if you can get the same turnaround performance.

Oh - and this dev box is the old slow one - we use for legacy testing :: on the dual core - its almost instant.

Westa

 

 
New Post
3/21/2007 5:38 AM
 

Nice time.

I don't know exactly on my box how long it takes (actually didn't even try it on this one... tried it last time some 6-7 months ago on my older one).

It's good that you have that timing, sounds ok.

 


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.0DNN4 - Vladan.Strigo.NET or DNN Suggested Dev Environment?DNN4 - Vladan.Strigo.NET or DNN Suggested Dev Environment?


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