Configuration :: Publish Website On Windows Server 2003, When It Is Devloped On MS VisualStudio? 2010
Mar 30, 2011
I am installing MS Visual Studio 2010 on my PC and will develop website on it. I have developed my old asp.net websites on MS Visual Studio2005.Our webserver where we publish our websites on Windows Server 2003.I want to know that whether we can publish websites develop in MS Visual Studio 2010 on Windows Server 2003?
when I deploy a website in IIS Windows Server 2003 R2 . First time deploy, it seemed no problem at all (fyi, the one who deploy for the first time is not me, but my friend) but after one or two days this problem occur. I can't browse from IIS and Internet Explorer. In Internet Explorer the page display:
"Internet Explorer cannot display the website." The worse, no error log data ever produced in Application category in Event Viewer.
I've tried change the address from localhost to 127.0.0.1 but the response is still the same. I even tried access just localhost alone. It should display the default homepage from IIS but the response is still the same too. I've checked IIS' Web Service Extension, the Active Server Pages and ASP.NET 2.0 are set to allowed. I also have tried make a virtual directory with just index.html inside and the response is still the same.
FYI: The server seems run in 64 bit (HP Proliant server). The website I build only used ASP.NET Ajax 1.0 and Crystal Report for VS 2005. From the server, I can access the internet but not the localhost.
we created an outlook addin 2003 in vs2008. We just moved to vs2010 and when we debugging the project it showing that required version of office is not installed.Is there any possible way to use the outlook addin 2003 in vs2010.Because i need to work my addin in all versions of outlook from 2003-2010 and i have to use vs2010 only.
I'm running windows 7, so I installed on my machine the oracle client version 18.104.22.168.0 (ODP.NET - Oracle.DataAccess version 22.214.171.124) . I'm trying to deploy an asp.net web application to a server that is running windows 2003, which has the oracle client version 126.96.36.199.0 (ODP.NET - Oracle.DataAccess Version 188.8.131.52)
I've been given a virtual dev environment being windows server 2003 and I need to publish a web app to it. I've deployed apps quite easily using the publishing wizard but I'm not sure how to do deploy to a windows server.. can someone please provide a link or a guide on how to do this as I need to set it all up and I really don't know where to start.
I'm trying to deploy my MVC 2.0 web application to a Windows 2003 server with IIS6, and can't find the means to do it. I read about clicking Build/Deploy, but I don't have this showing on my menu, and I have the professional version.
I have a really weird problem that I've been investigating for at least one week now. I deliver a website hosting both ASP classic and .NET 3.5 content in IIS6 on a Windows 2003 server environment with MySQL db backend. The solution has been installed on several servers (some hosted in WMWare) with no problems. On one specific server, also hosted in WMWare, the user experience great performance issues on the website. The problems are most seen when using database resources and is not limited to either .net or asp classic, but I am still not sure that the problem is only related to database calls.
Following components are involved:
IIS6 .NET FW 3.5 MyODBC 3.51 / 5.1 MySQL 4.x
Code executed on the server using all resources above runs smoothly when the IIS is not involved. The website shows times up to 2 minutes to execute code that takes 2 seconds outside the IIS. The exact same code is executed. Using profiling tools, I've seen that the great loss comes within calls to unmanaged code, for example when System.Data.ODBC namespace to calls into myodbc.dll.
The tricky part is: If at least one console user is logged in to the server, the performace problems are not seen anymore. When the user logs out, the problem appears again.I have tried to reinstall all components above, tried different versions of MyODBC, tried different website authentication methods, tried to run website under administrator privilegies, installed various MS KB's with no success.
I have built my site using VS.Net 2010 on my XP machine. I would like to deploy it to my server which is a Windows 2003 Server. I have tried to do it with FTP, but it keeps failing with the error that "Front Page Extensions are not installed on the web server". When I check the server the extensions were installed and I also checked IIS and the service for the extension is allowed.
We have multiple websites deployed onto Windows 2003 WebServer running under .NET Framework 2.0 SP1 version and now we want to upgrade it to .NET Framework 2.0 SP2, so just wanted to check that after upgrading the .NET Framework on the server do we also need to re-deploy the websites by recompiling them in .NET Framwork 2.0 SP2 version or it's not necessary as they will automatically start referencing the latest assemblies?
I need to deploy an asp.net 4 website on a windows server 2003 remote server. I have updated the server's .net framework to 4.0 and installed IIS 7. how to deploy the website because I have no idea how to.
I want to deploy asp.net 4.0 web site on windows server 2003, Now I already have a classic asp site running on it. Would there be any problem if I install .net 4.0 framework for my new site. Will the existing site (the one in classic asp) be affected?
Can someone point me to a step-by-step guide on how to deploy ASP.Net applications to a totally empty and brand new Windows 2003 Server?The server has ASP.Net and the .Net framework installed on it. IIS is up and running. I have created a new application pool.
I have an application which is used by others on different server without problems. The app was programmed by a programmer who is not available now. It was developed on .net 2.0. The windows 2003 is a new server, asp.net is enabled. from iis, I can configure it to use asp.net 2.0....,
but, when I load the site, it always show the 404. even after I change the default.aspx to a blank page, it still shows 404. however, if I put a default.htm in the folder, and it can be loaded without problems.
what can cause this? how to fix it? if I installed a vs2005 express on the server, will it fix the problem?
it seems the asp.net 2.0 dll is not recognized on server. never had this problem before.
I have been trying really hard to activate and launch a COM object using an ASP.NET web application. The aspx website has a code-behind file that has a reference to this COM object (which is an actual application -a CAD software). When required, the VB code creates (or launches) the application.
The complete set-up works in a Win-XP (32-bit) environment both under debugging using visual studio and when the website is accessed by an outside user (through IIS server in XP). But the same application doesn't get activated when it is hosted onto the Win-2003 (32-bit) IIS server. I get "Object reference not set to an instance of an object" error.
The way I have setup in Win-XP was to grant ASP user and Internet guest user permissions to the COM object in the DCOM Config and since the windows firewall is enabled, I add the exe file (associated with the COM object) to the exception list. For the case of Win-2003 server, I add the Network Service permission to the COM object. But the setup doesn't seem to work at all. I am not sure what I am missing and how to get the application to launch.
I have the same issue, I have added the On before the Application start, or Session Start and it is still not working.Application_OnStart or Application_Start is not firingSession_OnStart or Session_Start is not firing..Note that in my development environment it is firing (both of the names).When I am adding the Global.asax file, there is only one file (no .cs file). And when I am publishing the project, I am not getting the Global.asax file, I am getting a xxxxGlobal.asax.dll file on my bin folder...
We are running asp.net website on windows server 2003 with framework 2.0 and asp.net ajax 1.0 extensions. now we planned to migrate websites to windows server 2008 r2. since my websites on framwork 2.0, I need to install same framework on windows server 2008 r2 but I didnt find 2.0 version for windows server 2008 r2. Is it possible to install 2.0 version on windows server 2008 r2 ??
I've created a website and now I'm trying to publish it on web server but I'm getting a lot of errors related to 'web.config' that website working fine in my VS2010 but I don't know what's the problem on the server I'm getting following error:-
If I remove whole line 6 then it show error in line 7and so on, I've use radcontrol tool in my web application but whatever I've used they are working fine on my system.
I am trying to publish my web site on another server. I went to build menu and then selected publish. I did [URL] of the web site When I hit the publish button, I got the error publish failed. How can I see what is the reason for publish being failed. Also, Is their any other way, i can publish the web site. the server that I am publishing my web site is windows 2003 server. I am using visual studio 2008. The IIs version is 5.2 R2
I am trying to run an aspx file on my server windows 2003 with IIS 6.0. I get the following error. Server Error in '/' Application. Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
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 <customErrors> configuration tag to point to a custom error page URL.