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.0Team System & DNN - Best PracticesTeam System & DNN - Best Practices
Previous
 
Next
New Post
10/12/2007 1:57 PM
 
eMicBra

Joined: 9/2/2004
Posts: 12

AdefWebserver wrote

 ITLackey wrote

I like the idea of a project per module; I assume this requires you to use the complied module template.

This would not require the compiled module template. As you know I don't use the compiled module template. I only use the dynamic module format. In the DotNetNuke source control, the Survey module is a separate project and it is in the dynamic module format.

Works fine :)

Does any one know if this is possible (creating a project that contains only the files relevant to a single moduel) using Visual SourceSafe with the Web Site (rather than the Web Application) project type?

I have done quite a bit of Google research and experimenting but I haven't been able to find a way to add only the folders relevant to a single module to source control using Visual Studio 2005 and Visual SourceSafe while also using the web site project type.  A web site project in Visual Studio for developing a DNN module contains all the files and folders on the site (which includes the whole DNN installation) but I want to add only the ~/DesktopModules/MyModule and ~/App_Code/MyModule folders to source control.  The objective is for each developer on a team to have an identical DNN installation on their local machine which is not under source control, and be able to check out/in only the files related to a particular module.

Any advice is appreciated.
 
New Post
10/13/2007 11:48 AM
 
Ian Lackey

Joined: 7/22/2006
Posts: 127

I would like to acchomplish the same thing using TFS and VS2005. The core have it figured out, so we know its possible, but I cannot figure it out either. Here is the issue I run into:

My source code folder structure is something like this:
C:\Code
C:\Code\Business Name
C:\Code\Business Name\Customer1
C:\Code\Business Name\Customer2
C:\Code\Business Name\Customer3

All folders and files for the various customer projects are under the associated folders (ie. Customer1). Each of the Customer folders are associated with a Team Project. 

What I would like to do is have a shared DNN installation located at C:\Code\SharedDnnSite that will host the DesktopModules\ModuleName and Skins\Conatiners folders for each of the customer projects. The issue that I have is a warning from TFS that since the files are not located "under" the solution folder they might not be handled correctly by version control. Is this a legit warning, and if so what am I doing wrong to prevent this error?
 
New Post
10/13/2007 6:04 PM
 
AliCommerce

www.AliCommerce.com
Joined: 8/8/2007
Posts: 238

ITLackey wrote

I like the idea of a project per module; I assume this requires you to use the complied module template. I have not had much luck witht he compiled modules, I guess I am too accustom to the traditionally web site structure and ways of editing them. With that said, I guess its time to defy the laws of tradition and switch to WAP's.

The reason I added a site to source control for each project was mainly workspace mapping issues. IE. I need to create a skin for project A and one for Project B. It was just easier to throw together a site add a skin using the template and go to work. I have not tried it, and would love input on, mapping your source control to a skin folder inside of your local DNN dev site. would this work? Is there a better option?

I use WAP propose by this guy: vladan.strigo.net/Resources/tabid/82/Default.aspx. One of projects I worked on has 14 project files and 1000+files.  WAP mentioned above works great.

Frank Wang
 
New Post
10/14/2007 11:34 AM
 
Néstor Sánchez


www.nestorsanchez.net
Joined: 11/15/2003
Posts: 1986

ITLackey wrote

I would like to acchomplish the same thing using TFS and VS2005. The core have it figured out, so we know its possible, but I cannot figure it out either. Here is the issue I run into:

My source code folder structure is something like this:
C:\Code
C:\Code\Business Name
C:\Code\Business Name\Customer1
C:\Code\Business Name\Customer2
C:\Code\Business Name\Customer3

All folders and files for the various customer projects are under the associated folders (ie. Customer1). Each of the Customer folders are associated with a Team Project. 

What I would like to do is have a shared DNN installation located at C:\Code\SharedDnnSite that will host the DesktopModules\ModuleName and Skins\Conatiners folders for each of the customer projects. The issue that I have is a warning from TFS that since the files are not located "under" the solution folder they might not be handled correctly by version control. Is this a legit warning, and if so what am I doing wrong to prevent this error?

You can handle all projects like [desktopmodules\businessname\CustomerX] and then add only the module root for each directory to TFS. For the module to work itself, just make sure the references are correct for module installation in DNN. Be aware that I am suggesting this based on a WAP module. When you are using the Website method, the solution is to just add the directories and files you want for each project.

 

Do you know the truth when you hear it?
Néstor Sánchez
The Dúnadan Raptor -->Follow Me on Twitter Now!
 
New Post
10/17/2007 10:27 PM
 
Ian Lackey

Joined: 7/22/2006
Posts: 127

This is what I came up with to get just the folders I need into source control without mapping all of DNN. These steps assume that you already have a working install of DNN locally and have not (and will not) added it to source control. So the scenario is, you have a local development install working, and now you need to create a custom skin for a new project.

  1. Create Team Project
  2. Setup Project Folders for additional Projects, documents etc - Optional I usually create several folders in source control for each project (Documents, Lib, Production, Spike, Tools etc.)
  3. Add a folder for Skins and a folder for containers to source control
  4. Create a new portal on your development install
  5. In the new portal folder create the Skins and containers folders
  6. Back in Source Control Explorer edit your workspace and map the skins and containers folders in source control to the two folders you just created.
  7. Creat a new blank solution and add it to source control
  8. Bear with me, Add an Existing Website to your solution, provide the path to the Skins folder that you created in step 5
  9. Repeat this and open the containers folder created in step 5

---Optional--- If you do this you may still need to add and edit files using the two website projects created above.
Add existing website and open your development install
Cancel the Add X Project to Source Control dialog, and click OK to the failed mapping error

-------------------

Suggestions for process improvement are encouraged! There has to be an easier way to get this done. Plus it just feels funny having a "website project" in your solutions that simply points to a DNN sub-folder... am I way over engineering this or is this just how it has to be?

 

 

 
 
 Page 2 of 3
Previous123Next 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Team System & DNN - Best PracticesTeam System & DNN - Best Practices


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