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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Modifying an existing Project for v4.0.2 using VS2005...Modifying an existing Project for v4.0.2 using VS2005...
Previous
 
Next
New Post
3/8/2006 2:28 PM
 

Can someone explain in simple terms, please, how to take a DNN module project like say the Blog or New projects, make a simple change, compile it, and then re-install it into a test instance.

I downloaded both of these projects, and the surpising thing to me is that they are identified as being vs2003 solution files.  When I attempted to load them into vs2005, the new module choked, which converted the solution and project files, but none of the code was brought into the solution, the only error was given as conversion errors. So I was wanting to get some expert steps on how to do it, before tyring another. 

How is it that the download projects for DNNv402 have vs2003 files in them?  Are all of the DNNv402 project downloads similarly affected? Is anyone else seeing the issue?  If so, how are you getting around it.  This old dog needs to learn new tricks (vs2005), so I'm patiently waiting for an answer or two or three...

I'm using XP Pro, vs2005 std, and slq2005 std.  Please, don't recommend reading the doc, as I've done that, and I've found none that use this setup or detail using an existing project solution, changing it, compiling, and installing it.

If such doce exists, I will read it, but I've searched and can't locate any. Thanks for taking a look and helping...

 
New Post
3/8/2006 3:49 PM
 

If you were wondering about the answers to this post...

The only parts of DNN converted to asp.net v2.0 were all specific to the core code.  None of the DesktopModule projects were converted, as yet.  (Ok, maybe someone has done it, but for the most part - not yet officially.) 

So, you can continue to use vs2003 to make changes to these projects and install them into a DNNv4.x, which they will still run on.

Isn't the sky falling where you are too?

Thanks to my Seattle buddy for the answer. 

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Modifying an existing Project for v4.0.2 using VS2005...Modifying an existing Project for v4.0.2 using VS2005...


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