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.0Debugging .NET Nuke Core and Custom Modules with Visual Studio ExpressDebugging .NET Nuke Core and Custom Modules with Visual Studio Express
Previous
 
Next
New Post
4/27/2006 3:31 PM
 

Hello,

Let me start of by saying I'm running visual studio 2005 express on XP home which probably isn't ideal.

I'd like to be able to debug the core dlls and the custom modules I purchase. I change the code quite a bit but I'm not really able to debug. My current process is read the code, change the code, then test it. I can't step through it.

This maybe as simple as dropping the code behing pages in the app code folder instead of using the dll's but I'm not really sure.

Is there any documentation on this.

In VB6 I've done a lot of ASP work with VB based dll's being used for data access. In VB6 I could check a box to wait for components to be created and then when I used an app that used that dll I could debug the code.

Does VS2005 Express have a similar way of doing things.

 

 
New Post
4/27/2006 4:09 PM
 
I couldn't tell you if VS Express supports this or not, but to debug in VS, you go to Tools > Debug Processes... and attach the debugger to the ASP.NET worker process.

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com
 
New Post
5/3/2006 3:02 PM
 

VB Express doesn't support attaching to a process so it looks like I need to upgrade.

The other thing I'm looking at is moving all the .vb files to the app_code folder and using codeSubDirectories for each assembly but this could be a little time consuming and I don't even know if it will work. I would they try to debug with web developer express instead of vb express.

Figures that microsoft will give you something for free but remove things like the ability to debug a dll! Who needs that?

 
New Post
5/8/2006 9:08 AM
 
You might want to wait for the 4.2 release (not yet planned). This release might have support for the new web application project files. Not sure how this will affect any of this. Then again, the debugging issue isn't new to .NET 2.0.

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Debugging .NET Nuke Core and Custom Modules with Visual Studio ExpressDebugging .NET Nuke Core and Custom Modules with Visual Studio Express


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