I am just beginning to develop applications in VB.NET using the visual studio 2005. I am relativly new to .net as I have been doing my development in VB6. I am running a SQL 6.5 soon to be 2000 compatiable DB database.
Currently I compile a VB6 exe and place it on a network share, this allows for all users to access it as well as makes doing updates easy, which are frequent.
I have tried this in .NET and the application will run, but as soon as I make a call to my SQL database I guess .NET is saying it's in the local intranet namespace, and the app isn't trusted there, and it throws a SQL client error.
Could this have to do with how the SQL connection string or connection is beng made? The current string uses trusted aka windows security...
I have done some reading and one suggests making the app a trusted namesopace on the local computer (this of course woudl then have to be done to each user PC for each application, not a very feasible idea)the other is to open up being trusted to all on your local intranet (but i guess this isn't recamended)
I can't be the only one attemptiong to deploy a VB.NET application in this sense, is there a standard to which this is done? There must be a way to place a .Net exe on the network share for all users to access???
Thanks muchly, I know this is a bit of a read, but let me know if you need any further info, and I'm open to just about any suggesstions.
Copper
Currently I compile a VB6 exe and place it on a network share, this allows for all users to access it as well as makes doing updates easy, which are frequent.
I have tried this in .NET and the application will run, but as soon as I make a call to my SQL database I guess .NET is saying it's in the local intranet namespace, and the app isn't trusted there, and it throws a SQL client error.
Could this have to do with how the SQL connection string or connection is beng made? The current string uses trusted aka windows security...
I have done some reading and one suggests making the app a trusted namesopace on the local computer (this of course woudl then have to be done to each user PC for each application, not a very feasible idea)the other is to open up being trusted to all on your local intranet (but i guess this isn't recamended)
I can't be the only one attemptiong to deploy a VB.NET application in this sense, is there a standard to which this is done? There must be a way to place a .Net exe on the network share for all users to access???
Thanks muchly, I know this is a bit of a read, but let me know if you need any further info, and I'm open to just about any suggesstions.
Copper