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
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...dotnetnuke on shared drivedotnetnuke on shared drive
Previous
 
Next
New Post
3/9/2009 11:02 AM
 
john held

Joined: 3/9/2009
Posts: 19

We'd like to run VS 2005 on our onn PCs and access the dotnetnuke project on a production server

After tweaking the register on both the server and my own pc, I can add a web form and it will run without the dreaded "Network Bios command limit has been reached" error.

However, we're getting this now:

The file "I:\DotNetNuke\App_Data\Database.mdf" is on a network path that is not supported for database files.
An attempt to attach an auto-named database for file I:\DotNetNuke\App_Data\Database.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.

Any solution, or should we just install VS 2005 on the server?

Thanks!
 
New Post
3/9/2009 2:14 PM
 
Jeff Cochran


Joined: 6/3/2005
Posts: 2799

First, why are you using VS to work with DNN?  Anything you do should be done as a module that can be uploaded to DNN on the production server.  But your real problem is you don't have a proper connection string to the database on your server defined in your VS project.  You don't want to attach an auto-named database, you want to use the existing database.

Jeff
 
New Post
3/9/2009 2:39 PM
 
john held

Joined: 3/9/2009
Posts: 19

Thanks Jeff.

On using VS to work with DNN, it would be useful to be able to create some separate web pages which have some c# capabilities -- email and the like.  It seems like this would be simpler than creating a module to upload.

Naturally we'd want to use the existing SQL Server database in the DNN project--not sure where that string is defined.

Does this make sense?

 

John

 
 
New Post
3/9/2009 4:11 PM
 
john held

Joined: 3/9/2009
Posts: 19

..and answering myself after a further look:

I'm understanding a little bit more about the dotnetnuke architecture--looks like modules areessentially .aspx pages in a directory under desktop modules.

the DB connect string is defined in the web.cfg file.

The problem I am having is that Microsoft doesn't want one running Visual Studio on a production server--however deploying a dotnetnuke website which is both scripts and a database looks quite troublesome.

Any thoughts would be appreciated.

John

 
 
New Post
3/9/2009 4:16 PM
 
Alex Shirley


Joined: 1/30/2006
Posts: 5038

JOhn I would do the development on your local machine, then deploy to your server. Clone you server installation (inc database) locally, then deploy the changes.

I would not recommend installing VS on your server (although I had to admit that I did it in the early days :).

Thanks...

 

Alex Shirley
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...dotnetnuke on shared drivedotnetnuke on shared drive


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