Remote Development of VB.NET Application

  • Thread starter Thread starter Varkey
  • Start date Start date
V

Varkey

Dear all,

Can you please provide some information on the following issue, at the
earliest.

I have a development server setup in the network, say machine X. Also,
there is another workstation, say Y, for a programmer, to work with.
The application is a Winforms Application and machine X (server) does
not have Visual Studio .NET installed on it. Machine Y(workstation)
has got Visual Studio .NET installed on it. Y is connected via
sourcesafe to the solution in X, without making a local copy( I mean
through a network share).

There are issues faced by the programmer, in executing the application
in X, via Studio environment in Y. Basically application is not doing
any database related activities, and throws exceptions and breaks at
will.

Will this kind of a scenario ever work??? If not, please detail a
suitable alternative.

Two constraints are
a> No direct access to the Server X is possible for development.
b> Things need to be stage managed from the workstation Y.

Please respond at the earliest.

Regards..
Varkey
 
What kind of app, windows or web?

The most likely cause is the user the app is running (or debugging) under
does not have permissions for the database. The most common reason is you
are using integrated security and the process is running under an account
without db access. This is very easy to explain with a web application.

1. User hits app
2. User is anonymous, so he is authenticated as the local account
IUSR_ComputerName
3. IUSR_ComputerName is a local account, so it has no rights to anything on
the domain
4. You have given a Domain Group, or list of Domain Users, rights to SQL
Server
5. As IUSR_ComputerName is not a domain user, or in any domain group (and
cannot be due to the security model), data access fails.

Possible solutions
1. For web apps: get rid of anonymous access to the app. This will force a
log on for all users using the app. Not a good situation for Internet, but
great for Intranet.
2. Impersonate a particular user for database access. You can change the
user context of the worker process thread ... for both windows and web
applications.
3. Switch to SQL security and change the connection string to use a SQL
account. If you do this, encrypt the connection string.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
Author: ADO.NET and XML: ASP.NET on the Edge

****************************************************************************
****
Think Outside the Box!
****************************************************************************
****
 
Dear Gregory,

Thanks a lot for the response.

I am afraid, the application being a Winforms one, I am not able to
implement steps you have suggested. However extending your line of
thought into a Winforms app, let us assume, I have no access to the
database server from "P3", the server in which the application
resides. In this case, is it possible for me to specify somewhere in
the VS.NET IDE,that while trying to debug or run the application,
please use this particular USER ID to connect???
Or is it something entirely different I am thinking off, away from
what you were pointing to??

Thanks once again..

Regards,

Varkey
 
Back
Top