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 CommunityCommunity Membe...Community Membe...Free Tutorial: Automating Visual Studio 2005 for DNN Module DevelopmentFree Tutorial: Automating Visual Studio 2005 for DNN Module Development
Previous
 
Next
New Post
2/17/2006 2:27 PM
 

Tired of always running those SQL scripts to register your new DotNetNuke Modules?  Here's how to automatically do those tasks, and a lot more.  Visit the Visual Studio 2005 Tutorial here.

    - Doug Vogel     

 
New Post
3/6/2006 4:42 PM
 
Doug,

First let me thank-you for the macros.  Very nice addition to the DNN developer's toolkit and much appreciated.

however, I am having a bit of trouble getting it to work with VS2005 and I was hoping you might steer me in the right direction.  Basically, it appears that my module folders are being produced outside of the DNN starter kit folder and that is casuing an error with the macros.

Everything is fine up until the part where it tries to switch focus and then I get the "hresult" error from (as best as I can tell) the fact that the module template folders are not created inside the starter kit folder.  Is there somethign I misssed in your step-by-step instructions perhaps?

I was trying to "cheat" and just use the macros with minor mods.  Or is there some environment setting I missed in the details.  i will try to troubleshoot further, but I thought perhaps you might have traveled this path already.

thanks again for this time saver,

-eric
 
New Post
3/7/2006 9:51 AM
 
emaynard wrote
I was trying to "cheat" and just use the macros with minor mods.

You are correct being non-optimistic on success with minor mods (so be reluctant in trying that.)  The “Automating 2005 VS Pro Tutorial” is meant to be a learning experience and if you master what’s going on inside the code, it helps you realize how these things could be further useful as you do more  work.
So what I have so far with the Tutorial is mainly an introduction.  Now I am watching to see what level of interest there is - I won't add anymore if none is there. 
If interest level warrants, I might add more to the current tutorial, by showing how to automate common DotNetNuke code building tasks. 
It will be simply to continue, because after the “introduction”, your VS macros now know the
names of your view, edit, settings, resource files, etc.  These additional macros can then be exchanged/shared between developers.  Then presumably "free macros" could be offered as well as "free modules" between users.
 
So if you're having trouble, try first to manually create using Shaun's post.  Then run the macros.  Try running the Test_002() macro in the download.  This is the folder where the module will be created (not the same as where the starter kit location is).  You'll see the macro doing the same things that you do with the keyboard - and a little more.  Your macros will work because they only do the same things that you do via keyboard.

    - Doug Vogel     

 
New Post
3/19/2006 5:40 AM
 

Thank you for your tutorials on DNN!

Like emaynard, "Everything is fine up until the part where it tries to switch focus and then I get the hresult error" (invalid arg error) due to the following line:

DTE.ActiveWindow.Object.GetItem(myprojectname).Select(vsUISelectionType.vsUISelectionTypeSelect)

However I followed the instructions very closely. Even in Test_002, I selected AssemblyInfo.vb in the Solution Explorer, ran Test_002, and got the hresult error. The selected item did not change focus ...

myprojectname is evaluated to my project directory, equal to the first line in the Solution Explorer
DTE.ActiveWindow.Object evaluates to {System.__ComObject}
The trouble seems to be the GetItem method not defined.

I'm using Visual Web Developer 2005, Version 8.0.50727.42 on .NET 2.0.50727.

Any help ? 

Any work around? maybe some "help" by preselecting the project with the mouse?

 
New Post
3/21/2006 9:56 AM
 
For readers of this thread: I believe some of these things have been resolved (hopefully all).  Please take a look here if you are experiencing troubles.

    - Doug Vogel     

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityCommunity Membe...Community Membe...Free Tutorial: Automating Visual Studio 2005 for DNN Module DevelopmentFree Tutorial: Automating Visual Studio 2005 for DNN Module Development


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