SQL Server administration and T-SQL development, Web Programming with ASP.NET, HTML5 and Javascript, Windows Phone 8 app development, SAP Smartforms and ABAP Programming, Windows 7, Visual Studio and MS Office software Kodyaz Development Resources
Development resources, articles, tutorials, code samples and tools and downloads for ASP.Net, SQL Server, R Script, Windows, Windows Phone, AWS, SAP HANA and ABAP, like SAP UI5, Screen Personas, etc.

Software Development

Do not leave previous source code files on an ASP.NET deployed web site application

Hello ASP.NET developers,

I had faced a strange problem on test servers after the deployment of our ASP.NET web site project which can be summarized as follows;

The web site application is successfully build on the developments computers and successfully published to a local folder.

But when the published web site content is moved or deployed on the test environment, some functions do not response as expected although no run-time error, etc occurs.

The applications runs smoothly as some code blocks did not exists ever.

During some investigation, I created new web site by using the published web site content where the Microsoft Visual Studio 2008 publishes the project. This codes were running perfect, but when deployed on test servers they were not. But the source of both sites are identical.

So this was a frustrating problem.

Then an idea of cleaning everyting on the test server, and re-copying and deploying the published content has rised. And doing that way bring the success.

On the web site root, there were .vb source files that were placed there months ago perhaps. But somehow, the new deployed ASP.NET application was confusing during the compilation process and some code blocks were not running as they were not processed by the compiler.

So, if you are using Visual Studio 2008, you know you do not need the .vb or .cs source code files of your ASP.NET web site application on the target deployment folder. Just deploy what the VS2008 publishes.

Trust in Visual Studio

One more topic talked about during this bug or problem resolving period was editing the web.config file and altering the debug="true" compilation option to debug="false"

Running ASP.NET applications on production servers (for our case on a test server) is assumed to be causing unpredictable errors on some cases.

Note: If you wonder, I have made the change <compilation debug="true" /> to <compilation debug="false" /> in the Web.Config file where I have deployed my ASP.NET web project

Published Tuesday, January 08, 2008 9:29 PM
Filed Under: , , ,


No Comments
Anonymous comments are disabled

About eralper

SQL Server administrator and T-SQL developer including BI components Web programming with HTML, HTML5 and ASP, ASP.NET and .NET Framework developer SAP ABAP and SAPUI5 development, Web Dynpro and Smart Form Siemens HiPath Center CTI development
Copyright © 2004 - 2020 Eralper YILMAZ. All rights reserved.
Community Server by Telligent Systems