VS.net web project deployment
-
I'm using VS.net 2002 Pro and recently completed a very nice working web project. I would like to deploy this web from one Window 2000 server to another. However the webforms containing SQL database links do not work. The SQL server name is the same on both servers (local) but the server names are different. It seems logical that one could simply change the code in the forms, however that does not solve the problem. I feel the real problem is a "projectname.dll" in the /bin directory. It's loaded with MS code and some readable code that clearly shows the SQL connection string from the development server. It does not respond postively to user changes. Deleting it prevents all the other non-database forms from working. It seems to be the heartbeat of the web project. How does anyone transfer a web from one serer to another and maintain SQL connectivity???? kevin@upgrade1.com
-
I'm using VS.net 2002 Pro and recently completed a very nice working web project. I would like to deploy this web from one Window 2000 server to another. However the webforms containing SQL database links do not work. The SQL server name is the same on both servers (local) but the server names are different. It seems logical that one could simply change the code in the forms, however that does not solve the problem. I feel the real problem is a "projectname.dll" in the /bin directory. It's loaded with MS code and some readable code that clearly shows the SQL connection string from the development server. It does not respond postively to user changes. Deleting it prevents all the other non-database forms from working. It seems to be the heartbeat of the web project. How does anyone transfer a web from one serer to another and maintain SQL connectivity???? kevin@upgrade1.com
Hello, double check that it's not simply a rights problem. For example, if the SQL server connection string looks fine and appropriate from the development server's perspective as well as the deployment server's perspective (and that would normally be the case if it's on the same network), it could be that the type of security you are using is the culprit. Check your method of authenticating with the SQL server and the rights that your development server automatically gets to the SQL server, versus the rights that the deployment server has. "projectname.dll" is simply your project compiled and linked so what it contains is nothing mysterious, it's simply what you see in the source code. "Things are more like they are now than they ever were before." -- Dwight Eisenhower
-
Hello, double check that it's not simply a rights problem. For example, if the SQL server connection string looks fine and appropriate from the development server's perspective as well as the deployment server's perspective (and that would normally be the case if it's on the same network), it could be that the type of security you are using is the culprit. Check your method of authenticating with the SQL server and the rights that your development server automatically gets to the SQL server, versus the rights that the deployment server has. "projectname.dll" is simply your project compiled and linked so what it contains is nothing mysterious, it's simply what you see in the source code. "Things are more like they are now than they ever were before." -- Dwight Eisenhower
Well, I’m doing better than previously. The web form now shows on the Internet. However the font type and color are now plain black text. Also the data grid does not show only the /div window shows below where the datagrid should be. I x copied the complete folder from one server to another, placing it exactly on the C: to duplicate its OEM placement. Also made the appropriate SQL connection changes (machine names are different). It seems the .aspx page is not getting information from the .aspx.cs (CodeBehind) page. Any ideas??? Kevin@upgrade1.com
-
Well, I’m doing better than previously. The web form now shows on the Internet. However the font type and color are now plain black text. Also the data grid does not show only the /div window shows below where the datagrid should be. I x copied the complete folder from one server to another, placing it exactly on the C: to duplicate its OEM placement. Also made the appropriate SQL connection changes (machine names are different). It seems the .aspx page is not getting information from the .aspx.cs (CodeBehind) page. Any ideas??? Kevin@upgrade1.com
You can view this page at www.cchapel.com/cchapelaspx/sermonexp.aspx
-
Well, I’m doing better than previously. The web form now shows on the Internet. However the font type and color are now plain black text. Also the data grid does not show only the /div window shows below where the datagrid should be. I x copied the complete folder from one server to another, placing it exactly on the C: to duplicate its OEM placement. Also made the appropriate SQL connection changes (machine names are different). It seems the .aspx page is not getting information from the .aspx.cs (CodeBehind) page. Any ideas??? Kevin@upgrade1.com
Um...before you said you had a SQL connection problem, you didn't mention that the form itself wouldn't show at all. I really don't know what the problem could be, sometimes it helps to make a very simple example and try copying it to the deployment server. Very simple as in no sql, nothing special at all, just a very simple project, with maybe a button and an edit control and a bit of code that processes the text in the edit control when you click on it, you know, just enough to test the basics first, then work up from there. One other thing to note is that the deployment server needs many requirements that may not be there which visual studio normally takes care of for you when you install it. If you view the Visual studio readme file on the installation CD there is a specific section regarding how to get the prerequisite requirements satisfied for the deployment server, (i.e. installing .net, configuration etc). There is also tons of info on doing that on the net, Googling should bring it up quite quickly for you, it did for me when I first tried the same thing. Easiest way though if the deployment server is under your control and you know that you probably didn't install anything special to it to run ASP.NET apps is to use the Visual studio installation CD to install the server components only, again, see the readme file for more. "Things are more like they are now than they ever were before." -- Dwight Eisenhower
-
Um...before you said you had a SQL connection problem, you didn't mention that the form itself wouldn't show at all. I really don't know what the problem could be, sometimes it helps to make a very simple example and try copying it to the deployment server. Very simple as in no sql, nothing special at all, just a very simple project, with maybe a button and an edit control and a bit of code that processes the text in the edit control when you click on it, you know, just enough to test the basics first, then work up from there. One other thing to note is that the deployment server needs many requirements that may not be there which visual studio normally takes care of for you when you install it. If you view the Visual studio readme file on the installation CD there is a specific section regarding how to get the prerequisite requirements satisfied for the deployment server, (i.e. installing .net, configuration etc). There is also tons of info on doing that on the net, Googling should bring it up quite quickly for you, it did for me when I first tried the same thing. Easiest way though if the deployment server is under your control and you know that you probably didn't install anything special to it to run ASP.NET apps is to use the Visual studio installation CD to install the server components only, again, see the readme file for more. "Things are more like they are now than they ever were before." -- Dwight Eisenhower
I ended up reinstalling IIS, .net 1.1, and MDAC 2.7 to get pages to show. However I'm puzzled on why I'm lost my text formatting. I does seem that only the aspx page is being read, not the (CodeBehind) pages. I've been reading and working on this problem for days now. I'll keep posting messages until I find someone with the same problem and solution. You can view this page at: www.cchapel.com/cchapelaspx/sermonexp.aspx