< xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />
Deploying-issues on Windows XP
I have experienced annoying limitations trying to deploy Visual Basic 2005 Express Edition applications with SQL-database connection on Windows XP. Besides, the debugging feature on other XP-identities than the one where VB was registered, has proven inadequate as well.
In my experience it is only possible to debug the application with database connection on one identity on XP – the one where Visual Basic 2005 Express Edition was first registered. When I try to establish a mdf-database connection on any other XP-identity an error message occurs.
Deployed run-time versions on XP, which have been published, are only possible to run on one identity on the target computer as far as I understand. If you try to install the deployed application on another XP-identity an error message occurs when you try to run the application. Besides, the identity where you install the deployed application with database connection needs Administrator privileges.
I can live with the fact that Visual Basic 2005 Express only functions properly on one identity on Windows XP. But it is no good if deployed versions of the VB-application can only run on the Administrator account, not on ordinary user accounts on the target-computers.
Have I missed something here Please let me know if you have any ideas concerning this matter. Is there a difference between Visual Basic 2005 Express Edition and the commercial version of Visual Studio 2005 in this respect
New Forum
Nishad S
Dear readers,< xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />
I just thought you should know that this thread has continued in the SQL Server Security-Forum. An SQL expert is now involved too, trying to figure out what is going on. The subject-string is the same and Ziper is still the author. In SQL Server Security-Forum, the description of the issue is more detailed than here. If you are interested, please take a look at the counterpart to this thread in the SQL Server Security-Forum. The link below may take you directly to that forum:
Kindly regards
Zipermanish_kumar
I would like to comment my previous message.
When you work with Visual Basic 2005 Express Edition on windows XP, and if your application contains references to SQL-databases, it is important that all identities be logged off before you open the particular identity where you want to work on your Visual Basic project. In my previous message I assumed that it was only possible to work with Visual Basic on one identity, the one where the version was registered.
This assumption was not quite correct. Actually, you may run Visual Basic applications with SQL-references on all identities on XP, provided that no other identities that are using the SQL-server are currently running.
For example, suppose you start your computer and log on the identity James. Then you switch identity, but you actually don't log off James. Then you log on the John identity. There you discover that it is impossible to create a new SQL-database in Visual Basic's Data-connections view. An error message appears. Why is that It is because the SQL-server is busy on the James-identity. To solve this problem you want to log off the John identity, don't just switch. Then log on the James identity again, and log off properly. All identities should now be logged off. Now you may log on the John identity again, and it is now possible to create an SQL database.
Concerning deploying applications for XP. This issue is similar to the one I just described. You cannot run the installation-file successfully on one identity if the SQL-sever is busy on another identity. You want to log off all identities before logging on the identity where you want to install the application. Same thing when you want to run the deployed application.
Question. Does this limitation exist only in the express-editions of Visual Studio 2005 as a drag on free-ware, or is it prevalent in commercial editions as well. I would like to know a little more about this before purchasing the standard or professional edition of Visual Studio 2005.
Best Regards
Ziper