"Copy Project" and SQL ???
-
Using "Copy Project" has it's drawbacks. It's nice if I only have very simple web pages without any database. Now in real world asp programming, that is using databases and web forms, the "Copy Project" will not reconnect any database connections or even ask me. Seems like a rather dumb idea by Microsoft. Any suggestions on simply transfering a finished web from a development server to an Internet web server??? ps. What's the point in having "automatic" features like "server explorer" to write all the code behind the scenes if its nearly impossible to make a simple web transfer??? The old fashioned way of coding all languages on a single asp page seems more dependable and easier to move.
-
Using "Copy Project" has it's drawbacks. It's nice if I only have very simple web pages without any database. Now in real world asp programming, that is using databases and web forms, the "Copy Project" will not reconnect any database connections or even ask me. Seems like a rather dumb idea by Microsoft. Any suggestions on simply transfering a finished web from a development server to an Internet web server??? ps. What's the point in having "automatic" features like "server explorer" to write all the code behind the scenes if its nearly impossible to make a simple web transfer??? The old fashioned way of coding all languages on a single asp page seems more dependable and easier to move.
For any serious project, don't use the drag and drop features to build queries or views / datasets etc, or at least, only use it to get an idea of what code you will need to add, then remove it and add it back yourself by hand. Reason being that I've found from experience is that the code built for database access (other than the connection string itself)by the wizard is often very strange and in many cases badly inefficient. In terms of moving a web that accesses a database server, all the normal things that apply to deploying any database project (web based or not) have to be taken into consideration. For example your app would normally build all the database objects it requires when it first connects to the server or as part of the installation script. In terms of a web built (for example in c# and asp.net with vs 2002/2003) I've never come across a case where it couldn't be simply copied to the production web server so I don't agree with you there. "Things are more like they are now than they ever were before." -- Dwight Eisenhower
-
For any serious project, don't use the drag and drop features to build queries or views / datasets etc, or at least, only use it to get an idea of what code you will need to add, then remove it and add it back yourself by hand. Reason being that I've found from experience is that the code built for database access (other than the connection string itself)by the wizard is often very strange and in many cases badly inefficient. In terms of moving a web that accesses a database server, all the normal things that apply to deploying any database project (web based or not) have to be taken into consideration. For example your app would normally build all the database objects it requires when it first connects to the server or as part of the installation script. In terms of a web built (for example in c# and asp.net with vs 2002/2003) I've never come across a case where it couldn't be simply copied to the production web server so I don't agree with you there. "Things are more like they are now than they ever were before." -- Dwight Eisenhower
J Cardinal wrote: For any serious project, don't use the drag and drop features to build queries or views / datasets etc Good advice. BTW, those things actually confuse me, so I head straight for the SQL view. Nothing like good ol' code! ;)
"Do unto others as you would have them do unto you." - Jesus
"An eye for an eye only makes the whole world blind." - Mahatma Gandhi -
For any serious project, don't use the drag and drop features to build queries or views / datasets etc, or at least, only use it to get an idea of what code you will need to add, then remove it and add it back yourself by hand. Reason being that I've found from experience is that the code built for database access (other than the connection string itself)by the wizard is often very strange and in many cases badly inefficient. In terms of moving a web that accesses a database server, all the normal things that apply to deploying any database project (web based or not) have to be taken into consideration. For example your app would normally build all the database objects it requires when it first connects to the server or as part of the installation script. In terms of a web built (for example in c# and asp.net with vs 2002/2003) I've never come across a case where it couldn't be simply copied to the production web server so I don't agree with you there. "Things are more like they are now than they ever were before." -- Dwight Eisenhower
Indeed this is the most insane software I've ever used. You see, when I move a perfectly running asp.net web project to another server, the computer names are different. So I changed those to make sure the database connections are correct. However upon this attempt nothing works. Oh yes the server is quite capable of running asp.net pages. I suppose I would have to either develop all web projects on the actual Internet server to begin with or go back to the old fashioned way of writing all the code on a single .asp form including all c# scripts. I'm very dissapointed after spendng countless hours learning various drag-n-drop features only to find it's too complicated to be moved.:(
-
Indeed this is the most insane software I've ever used. You see, when I move a perfectly running asp.net web project to another server, the computer names are different. So I changed those to make sure the database connections are correct. However upon this attempt nothing works. Oh yes the server is quite capable of running asp.net pages. I suppose I would have to either develop all web projects on the actual Internet server to begin with or go back to the old fashioned way of writing all the code on a single .asp form including all c# scripts. I'm very dissapointed after spendng countless hours learning various drag-n-drop features only to find it's too complicated to be moved.:(
kvnsdr wrote: You see, when I move a perfectly running asp.net web project to another server, the computer names are different. So I changed those to make sure the database connections are correct. However upon this attempt nothing works. It's normal practice to put the connection string in an externally configurable place if it's production software or at least in only one place in your code if it's internal use for just this reason. Then you only need to update one place. As you found out, when you use the drag and drop features it will happily make a new connection string over and over and over again. I think that the drag and drop is an excellent way for a beginner to learn what is required to get the task accomplished, but then most would quickly move beyond that if they are programming more than a very simple application. "Things are more like they are now than they ever were before." -- Dwight Eisenhower
-
kvnsdr wrote: You see, when I move a perfectly running asp.net web project to another server, the computer names are different. So I changed those to make sure the database connections are correct. However upon this attempt nothing works. It's normal practice to put the connection string in an externally configurable place if it's production software or at least in only one place in your code if it's internal use for just this reason. Then you only need to update one place. As you found out, when you use the drag and drop features it will happily make a new connection string over and over and over again. I think that the drag and drop is an excellent way for a beginner to learn what is required to get the task accomplished, but then most would quickly move beyond that if they are programming more than a very simple application. "Things are more like they are now than they ever were before." -- Dwight Eisenhower
J Cardinal wrote: I think that the drag and drop is an excellent way for a beginner to learn what is required to get the task accomplished, but then most would quickly move beyond that if they are programming more than a very simple application. Goes for most visual designers). I always like to learn the ropes by doing things with the designers and then looking at the code they generate. :) That gives you a beginning foundation, but then of course you'll always need to go far beyond that.
"Do unto others as you would have them do unto you." - Jesus
"An eye for an eye only makes the whole world blind." - Mahatma Gandhi