My technique for deploying an ASP.NET webapp into production is as follows: Client: Select 'Release' mode and then right-click to publish. Go manually to the publish folder and zip contents. Now transfer to server by FTP.
Server:
Unzip folder contents. Stop IIS. Deploy new folder contents for web app. Start IIS. I don't stop the database or run any additional tools to promote to production. It's a small company, and this seems fine. What's wrong with this technique in your opinion?
I hate to sound stupid, but ASP.NET is not my forte. I have build an ASP.NET application which I now which to deploy to a production server. Searching on the web I found that it's recommended to just use the Setup tool within VS2010 to compile and install the files on the production servers. However, I find it a bit weird:
The files on the server are exactly those that I had on my system. I would've imagined that moving to a production server would involve some compiling and compression of file content so as to improve execution. But in practice all files on the server are exactly as they are on my local system -- I can even modify my .cs file on the servers and that works!! (Surprised ;-)). Following from the above, all my code is readily available on the server for anyone to see. I am not sure if this is a problem... For example, could it end up a security risk (due to passwords within the files)?
I am developing a MVC 2 application that uses aspnetdb on my SQL Server 2008 detabase for forms authentication. On my development machine I can configure the users, roles and permissions using my Website Administration Tool (WAT). My question is how do I deploy this database to a production server and how do I configure it with users, roles and permissions?
I'm trying to find the best server architecture solution to deploy monthly updates to an Asp.net external public facing website. What I'm looking for are ways to release a new version of a website with minimal impact to users. Besides deploying the standard way (ie. stop IIS, copy new website over existing website, start IIS), what are some "better" solutions for deployment out there? It would be nice if they kept their session and didn't have to see a "Website under maintenance" message during the update. My server configuration
We have 2 IIS web servers (2003) and are trying to figure out the best way to utilize them for deployments. My first thought was to update the non-active web server with the latest release. Then to gracefully point the web traffic to that server with minimal impact to users (best case, the user doesn't lose his session). How would you go about "repointing" the web traffic from server 1 to server 2? Changing firewall NAT? Changing DNS records? Some other way?? We need to be able to test the live site immediately after we release the new changes (duh). BTW, we are using nant and cruise control to automate the builds, and a custom web service to deploy the build to production. So it's all automated with the click of a button. Could a better solution be achieved using a 3rd server? If so how?
I am developing 2 Applications. One WebForms and the other is MVC. How can i secure the code such that when i deploy them to the clients production environment, they cannot be simply picked up, copied and repackaged by someone else?. I simply need a way to protect my intellectual property. Can this be done in Visual Studio 2010?
I have around 100 rdl report files...what i have found in google is -> open RS Admin site upload each report...doing this manually takes a lot of time... We don't want to use Target report server url method and clicking deploy option to deploy the reports or report project onto the report server...because we are not provided with such production server url information...!! In client perspective...We just give the reports as a rar file...now client will have to extract the report files...and what should be the next step...!! Is there anyway to deploy or upload all the reports at a time...!!
I have create a report in sql server 2005 & want to deploy on production server, in local system it deployed & works well. also if that report deploy at local system successfuly than how i see report in intranet.
Is it already possible to run a ASP.NET MVC 2.0 / NET 4 web site in production and later on the 12 of April to replace it with the final versions? I notice that the Microsoft Web Plataform Instalar includes NET Beta 2 ... Not Net 4 RC.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. oday i have create two pages login.aspx using LOgin control and register.aspx using Create user wizard ...when i use connection string of my production server in my local computer then site works only if my database ASPNETDB.MDF is present in APP_Data Folder in my local computer
Planning of using t4 template in a production environment. I have not used this before either. I want to know if anything is required to be installed on the production server, are there any settings to be configured on the server, etc.
Is there a way that I can trace every method, basically a line trace, in an asp.net web site in production environment?
I don't want to go about creating db logging for every line - i see an intermittent error and would like to see every line called and performed by the website per user.
I have this piece of code to handle the HttpRequestValidationException in my global.asax.cs file.protected void Application_Error(object sender, EventArgs e)
I have create click once application hosted in IIS and its working fine.Now how we deploy or publish it to production server. Just using my local vs2008 might not work.
where i can deploy application to production server which ofcourse does not have visual studio
So I'm trying to get away from Tables for positioning. I labored through making my page look how I want it to with CSS. When I run it through the debugger, it comes up looking how I want it to in I.E. 8. Then I publish it and run it off of IIS on a network server through I.E., and all the controls are lined up against the left side of the screen, stacked on top of one another.? My colors are correct so it is reading my style sheet, it just seems to be ignoring any positioning.
Can I objectively determine if my production ASP.NET web application is resetting its application pool? It could be for whatever reason (for example, an error occurred or memory topped off). I don't have direct access to my production servers, so when I want something on the server, I have ask specifically for it like PerfMon counters to run. It is a running IIS 6.0. I understand that I could use PerfMon to catch ASP.NET Application Restarts. If I was not monitoring that PerfMon, is there anything that can tell me the application restarted sometime in the past?
I have made changes to my global.asax file so i want to recycle my web application to make the changes work. How to safely recycle my asp.net web application in production server?
I'm using localReport to print PDF (SQL REPORTVIEWER). It works fine on localhost. When I move the application to Production (64 bits windows 2008) it gives me an error. (see below)
I put the renderedbytes in a Session in USERCONTROL and I do window.open('Program1.aspx')...
In page load of Program1.aspx I try to retrieve the Session variable and process.... I think this statement cause the error "Response.BinaryWrite (...) etc".
It works on my local pc (Vista 32bits)...
[Code]....
Server Error in '/' Application. Object reference not set to an instance of an object. Description: An unhandled exception occurred during the execution of the current web request. review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
I developed a web page using asp.net 2.0 and ajax toolkit on my laptop on Windows 7 and IIS 6. I have my ajax/atlas toolkit DLL in my bin. The updatePanel works fine and does not postback my page. But when i hosted my website on a dedicated server the page postback totally like i have no updatepanel/ajax in my page...
I am using : Windows server 2008, IIS 6Ajax 2.0 installed on the server. I don t understand what is the difference with windows server or IIS or something else?
The following .post command in a .js file works fine in Dev and Test but not on our production box (Windows Server 2003). I believe the URL is not being found on the production box since the function(result) is not being run. Or it could be that the index method is not returning the jsonresult.
We have a ASP.NET application working on our staging server/DB. The application works fine. We are using ASP.NET Memebership/Roles, etc.
Now it's time to deploy the application to production. As part of the deployment, we want to copy/migrate the ASP.NET Memebership database to the production servers.
Can we simply do this via SQL Server's export/import functions? Will the applications IDs and role IDs that move to the production DB make sense when the ASP.NET application is deployed on the new boxes?
We have been a ColdFusion shop for 10 years, and are now switching over to ASP.net MVC. Our target framework is .net 4.0 BETA 2 using VS 2010 BETA 2. We set up two instances of Windows Server 2008 (staging and production), and will be using our existing database server (SQL Server 2008).
None of us really have much experience in ASP.net itself, though we are all very comfortable in C# and the MVC pattern. The coding itself isn't much of an issue; but the deployment process is. Our goal is to be able to have a CI setup that will automatically pull down, and test, our applications into staging on commit - then have the option to tag, then switch, the checkouts on our production sites when websites pass QA.
Some of the things I'm having issues with here is the concept of an ASP.net application and how it integrates into SVN. CF, like PHP or RoR, are all scripting languages and as such require no build process (checking out the source into production is very straightforward). But in this case, applications need to be compiled - which is where we start to have problems. Will we need to create another server (or use an existing one) that has some sort of application that pulls down code, compiles it, then somehow pushes it on the live servers? If so, what is considered the best way to accomplish this? I imagine if we end up using a build tool such as Nant, adding additional steps to migrate the database would be trivial, but what is the best way to accomplish this as well?
Another, slightly unrelated, problem is how our designers will work with our code. Most of them are on Macs, and using VS isn't much of an option. How will they be able to edit the aspx, css and image files easily? Our goal is to make this as transparent as possible to them.
We have done a lot of shopping around, and ASP.net MVC seems to be the best option as far as our familiarity with the language, and our current platform. We just need to figure out a good build process so everything is as transparent as possible.
I have an ASP.NET project that also uses a SQL MDF File. My target server is SQL 2008R2 or SQL Azure.I would like to know what deployment options I have as I migrate from DEV to PROD. In case it matters I'm not under any regulation to maintain PII or similarly private data.
we cannot login to one of our asp.net production website. Once login ID and password are entered on the login page, the site just stays on the login page without giving any errors whatsoever and without opening the default page.
