![]() But then I exited the VS and returned later. I then setup the database in Visual Studio 2022 and at first it worked fine. My software I have also tested with SQL 2019 and it works fiine with that, if it works better with VS22 I could change the database engine. I have a database that is not attached that I use SQL 2014 with. Perhaps there are some settings that can be made in VS22 to prevent these problems?Ĭurrently I am going back to using 2019 as I can not waste time with database issues like this. It is only when using the server explorer in Visual Studio 2022 that the issues flare up. When running from my code, I have seen no database issues. And I like that the 64 bit adds so much capability for large programs. The really frustrating part of this is it will be working and then when I get out of VS22 and later reload, the reload seems to create the issue.įrom a programming standpoint, I use VB.net, the VS22 seems to be faster and improved over 2019 version. In some cases I had to use a backup copy of the database because the one that was in use became corrupted by VS22. The fix has been to delete the database from VS22 and then go into the SQL management Studio and reset up the database connection to the server. ![]() Now the database and the SQL2014 are using Windows Authorization so what is that all about? No problems like this with VS19. But this resulted in my being locked out due to authorization issues. I tired to go in and manually select the engine and other settings. This is frustrating because the connection string is there. First instead of just autmatically knowing the attached database is using 2014, frequently VS22 tries to use one of the local server engines. The new interface to databases is a bit different than the 2019 and that seems to be a problem. Normally in 2019 VS there is absolutely no problems with the database which is running locally on my machine using SQL 2014. Then it screws everything up in the database!! Sometimes I can get the database working properly in Visual Studio 2022, but too frequently it fails.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |