Newbie - Development vs Deployment with MSDE

  • Thread starter Thread starter Mike
  • Start date Start date
M

Mike

Hi all!

I have installed MSDE on the development machine.
Server Name = DevComp

When using the wizard to generate the SqlConnectCommand it sets the
server name to DevComp.

Thinking ahead to when I deploy this application...
The end user's computer will not be DevComp, it may be DaComputer (who
knows).

What is the best way of handling this?
 
Hi Mike,

Well there are many answers to your question, but first to set things
straight - MSDE, is SQL Server, only a stripped down version of it.

So as long as you specify the correct connection string, you should be fine
and dandy. Now, when you are developing thru a wizard, the wizard actually
writes code in the background, that you can easily modify to instead of
hardcoding a computer name, could put in the local computername instead.

I would highly recommend reading some good discourse on .NET and ADO.NET,
because wizards do not generate optimum quality code for enterprise
applications. I'd be biased and would recommend an ADO.NET title that I am
writing due for release in November, but for the meanwhile there are a few
other good books in the market.

- Sahil Malik
Independent Consultant
You can reach me thru my blog at -
http://www.dotnetjunkies.com/weblog/sahilmalik/
 
Mike

Use "(local)" as the server name. Note: make sure you take off the quotes, but keep the round brackets
(local) means that you are always going to connect to the SQL Server running on the local machine

Manish Jadha
 
Thanks Manish!

Would [local] only work when the application is on a stand alone
computer or also on a network? (Does each workstation have the SQL
Server running?]
 
Back
Top