Web Forms :: Display Xml File After Publishing To Production Server
Oct 18, 2010
In my Visual Studio 2008 web site, I created a new folder named Reporting. Then one of my web pages creates an xml file in this new folder when the user clicks a button. The user then clicks another button and the xml file displays in the browser. This all works fine on my development PC. But if I publish this web site to my production server, it does not work. I get an error when I click the first button to create my xml file. The error reads: Could not find part of the path 'c:windowssystem32inetsrvReportingabc.xml' What must I do so that this works on my development PC and also my production server?
I'm trying to publish a site which uses an ajax uploader control which has an extra licence file that must be in the bin folder. Now if i publish my site this file is not published to the server and so i have to manually copy the file every thime to the server. My publishing setting is set to 'Only files needed to run this application'. If I change this to 'All files in the project folder' then it works but what is the point in that? I'm using Visual Studio 2010 Ultimate. (Note that i am a little new to publishing websites etc).
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.
Created a new virtual directory on my web sit in IIS 6.. set proper settings and wild card extensions... published via file system from dev environment to the server but i get a page cannot be found 404 error when browsing the site...
I have an application that uploads an Excel .xls file to the file system, opens the file with an oledbconnection object using the .open() method on the object instance. The upload and writing of the file to the file system works fine but I get an error when trying to open the file on our production server only. The application works fine on two other servers (development and testing servers).
The exception comes on production server at connection.Open() some times, when I reset the asp.net worker process it started to work but after some hours/days It occurs again. how can I fix this issue which comes in production some times but very irritating, or there is some other work around.
I've never had this problem before, I'm at a total loss.
I have a SQL Server 2008 database with ASP.NET Forms Authentication, profiles and roles created and is functional on the development workstation. I can login using the created users without problem.
I back up the database on the development computer and restore it on the production server. I xcopy the DLLs and ASP.NET files to the server. I make the necessary changes in the web.config, changing the SQL connection strings to point to the production server database and upload it.
I've made sure to generate a machine key and it is the same on both the development web.config and the production web.config.
And yet, when I try to login on the production server, the same user that I'm able to login successfully with on the development computer, fails on the production server.
There is other content in the database, the schema generated by FluentNHibernate. This content is able to be queried successfully on both development and production servers.
I have a vertical menu placed on top of (z-Index) a background image. The background appears nicely on my development server but does not appear on the production server. I have deleted all folders and file from the appropriate directory on the production server and copied all files and folders from the dev server to the production server to no avail. I figure that there must be a setting blocking this functionality on the production server or perhaps that older version (Server 2003) does not support this function.Oh, I have been attempting to add 2 PNG images to this post but cannot succeed.
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's configuration tag to point to a custom error page URL.
My hosting provider gave me the connection string to connect to the SQL Server 2005 but it doesn't work...
I don't understand why my site was running fine using the production SQL Server 2005 in my local PC when I include ASPNETDB.MDF file in App_Data in my local pc only ..if I remove file ASPNETDB.MDF from App_Data of my local pc ... the site stops working ...
Can anybody tell em how to fix this ... !! I am very tensed since last 3-4 days
how to transfer my data from devlopment server to production server ,i have already records exist in my database if i go for script then how can i transfor record in script i can transfor only table ,procedure and views.I am using SqlServer 2005.
The file system I'm publishing to is a not hosted by me, but by my university. IT here offers students their own web directory to host a website. My intention is to use it to host projects for classes and demo them for my professors. You can enter in a specific link in any browser to go to this website and view it as long as there is a file named 'index.html' in the directory with some presentable html code.
So here's the problem. I want my website to be written using ASP.NET and when I use VS2010 to publish my ASP.NET website to the 'File System,' I cannot simply open up my browser, type in the normal link, and have it display. It just shows up as a list of files in the directory and I can see all my source code for the web site
recently converted a project written with VS 2008 + asp.net 3.5.The problem is that on line on the production server (that's running asp.net 3.5) it can't render correctly on safari.The project has a BrowserFile.browser that with past visual studio worked:
I am working on the migration of the server. Our new server is Windows server 2008 with IIS7.0 I have a great difficulty in browsing the pages hosted in virtual directories. I have followed the proper steps of creating a virtual directories and converting them into applications. But when i try to browsing the pages of the virtual directory, i get the 404 error. Note: The .Net Framework 4.0 is installed on the server and the web applications which i am trying to configure in the virtual directories are developed in Visual Studio 3.0. Even the http://localhost also don't work.
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.
I am wondering the best way to change my connection string based upon which server I am accessing.
Essentially, all of the development is done on our local machines - once we think it is working, we upload it to our development server. In these 2 instances, I want my application to go off of our "dev" connection string for the SQL database in the web.config.
However, once it is published to our production server (for an internal application), I would like the connection string to point to our live db.
I am using the N-Tier model by Imar Spaanjaars - and have it setup like he suggests - In my DAL I have a class called AppConfiguration -
In this class I have a public readonly property ConnectionString() which returns the connection string in the web.config.
This is in an individual class library. What I would like to do is something similar to:
If server is localhost OR devstring return devString else return productionstring
I m getting the following error when i upload my site to Production Server using Database in App_Data ASPNETDB.MDF
Server Error in '/' Application. Runtime Error Description: An application error occurred on the server. The current ustom error settings for this application prevent the details of the application error from being viewed [code]...
I built an ASP.NET 4.0 Web Site. It works perfectly on my development computer. However, when I deploy the web site to theProduction Server, which is a Win2003 Small Business with Sql Server 2000, the site can't connect to the database.
These are the different tests I've made:
I tried using Integrated Windows authentication and this connection string: Data Source=myServerAddress;Initial Catalog=myDataBase;Integratedsecurity=true; and the error I got was that NT Authority/Network Service couldn't open the database. So I added that account to my database users list and gave it the appropiate permissions. Nothing.I tried using Sql Server authentication, so I created a new database user with a password and changed my connection string toData Source=myServerAddress;Initial Catalog=myDataBase;User Id=myUsername;Password=myPassword;. Nothing. I still got the same NT Authority user message.I deleted the used I created in step 2 and used the same connection string, to see if this time I got an error saying something about my user, and indeed it happened. I got an exception saying that user myUsername couldn't log on. I then created the user again, ang got the NT Authority user message one more time.I created a console application that used the same connection string from steps 2 and 3, and it connected to the database witouth any problem, which made me think that my problem's got something to do with my Web.config.I tried enabling impersonation on my Web.config, and thos time I got the same error message, only referring to the user I logged in to Windows, instead of NT Authority/Network service. What else could I check? My Web.config is this in case it helps (I havn't really put anything into it other than what VS puts):
From the last few days I am struggling with the error
"Failed to generate a user instance of SQL Server due to failure in retrieving the user's local application data path. Please make sure the user has a local user profile on the computer. The connection will be closed." I hav created an asp.net web application with membership shcema. It works fine an my developement machine but when I published it on my web server.
I have installed Windows 7 Professional and Visual Studio 2010 on a machine I was using VS2005 on with Windows XP. I am unable to publish to c:inetpubwwwroot. The files cannot be deleted in wwwroot or edited. I turned off read-only and am still unable to edit anything in the root even when opening something in notepad. When publishing a site every file in the directory throws the following in VS.
"Error deleting file 'what_is_a_puppymill.aspx'. Unable to delete default.aspx'. This function is not supported on this system."