![]() ![]() ![]() What are the options? Well, one option is to use the encryption to encrypt the settings in app.config. While this may be fine for some people, what about the people like me that do not want my users to access that database? I don’t want them to have that username and password… While the chances of a normal user loading SQL Server Management Studio and logging in are slim, it’s still possible and it’s definitely possible if a user purposely wants to get out of having to do work that day. In order to run that in a production environment you have to set the connection string in the app.config file. But what if you send that application to someone else that has their own SQL Server?ĭid anyone at Microsoft actually use this scenario in a production environment? What were they thinking? ![]() Running it on the development machine (or on the same network) is no big deal and just works. The connection string is saved to the application settings file and that property is saved in the dataset. A new dataset is created with it’s associated table adapter. I don’t know how a lot of people handle it, but one thing that always bugged me about table adapters and datasets is the way it handles it’s connection strings. * Update – I have uploaded a sample project here for those of you still struggling with this. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |