I had a post last week about this and found a temporary workaround functional enough, but after a few days of holiday, I'm back to dealing with the reality of it.
My server's connection string alias isn't replacing my development machine connection string alias when published and run. If I make the local machine's named connection string that of the server's connection string and publish, it works on the server, meaning that the application server is operating based on the local named connection string. But for development purposes, the server's connection string doesn't work on the local machine for obvious reasons.
All had worked fine until I got a new development machine, on which I've loaded the latest release of Alpha, restored a backed-up database project, and attached copies of our database to the new machine's SQL Server databases. Because the new machine has a different connection string (note that only the PC name has changed--i.e. it was Bob\SQLEXPRESS and now it's Joe\SQLEXPRESS), I made the change in Alpha so that the local named connection string worked properly. But as soon as I published a grid to the server, the application server threw up server connection errors and caused significant problems until I figured out the workaround.
Can anyone tell me how to correct this problem? I'd be quite grateful.
My server's connection string alias isn't replacing my development machine connection string alias when published and run. If I make the local machine's named connection string that of the server's connection string and publish, it works on the server, meaning that the application server is operating based on the local named connection string. But for development purposes, the server's connection string doesn't work on the local machine for obvious reasons.
All had worked fine until I got a new development machine, on which I've loaded the latest release of Alpha, restored a backed-up database project, and attached copies of our database to the new machine's SQL Server databases. Because the new machine has a different connection string (note that only the PC name has changed--i.e. it was Bob\SQLEXPRESS and now it's Joe\SQLEXPRESS), I made the change in Alpha so that the local named connection string worked properly. But as soon as I published a grid to the server, the application server threw up server connection errors and caused significant problems until I figured out the workaround.
Can anyone tell me how to correct this problem? I'd be quite grateful.
Comment