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.0DNN & Visual SourceSafeDNN & Visual SourceSafe
Previous
 
Next
New Post
1/3/2008 11:34 AM
 

I downloaded DNN 4.08 and I need to check in the source to VSS.  I got it to build and got it configured for our SQL server no problem.  When I checked in the entire solution into source control it cause all kinds of build errors.  Am I doing something stupid or what?  Most of the errors are permission errors.  I added Everyone to the security tab and gave them full permissions, still no go.  Any help is greatly appreciated.  Thanks, Mike

 
New Post
1/4/2008 10:38 AM
 

Mike,

I am not aware of any reason that checking DNN into source control would break anything.

Can you post an example of an error that you are now receiving?


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
6/25/2008 8:47 PM
 
I, too, am having an issue with Sourcesafe. I checked in the whole (of a working) DotnetNuke Solution (some 34 projects) and then tried to run. At first it came up with errors in the Bin file permissions. Having then checked out the whole of the Bin file from Sourcesafe I re-ran the program. This time it actually ran. I then checked out one of the ascx modules and made a few changes. Now, when I try to rerun it, it only comes up with a 404 Error saying it cannot find localhost/Dotnetnuke_2/Default.aspx .
 
New Post
6/25/2008 9:01 PM
 

Mike wrote

I downloaded DNN 4.08 and I need to check in the source to VSS.  I got it to build and got it configured for our SQL server no problem.  When I checked in the entire solution into source control it cause all kinds of build errors.  Am I doing something stupid or what?  Most of the errors are permission errors.  I added Everyone to the security tab and gave them full permissions, still no go.  Any help is greatly appreciated.  Thanks, Mike



The permission that you should have is write permission for the aspnet_wp account (ASPNET or NETWORK SERVICE usually)

Checking it in shouldnt break it :) Maybe it is choking on the .vss files somehow, but it shouldnt

Also, you dont need to compile DNN to use it.  It runs just fine without compiling.

JK.


You know your website is cool, so why not let your users help you by spreading the word on social networking sites - get the DotNetNuke Social Bookmarks Module with 57 different ways to add social bookmarks to your site ... or download the FREE demo right now
 
New Post
6/26/2008 5:13 PM
 

When you check it in into Sourcesafe all files will be set to read only. This may be causing problems as DNN needs to be able to change the files.

Stephan
Dotnetnuke Modules

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0DNN & Visual SourceSafeDNN & Visual SourceSafe


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