aspnet-compiler

aspnet_compiler on Mono

廉价感情. 提交于 2019-12-04 14:49:39
I'm trying to write a build script for a ASP.NET MVC 3 web site for publishing on Mono. Although some devs use Windows for development, the site must be built on Mono, as the build and Web servers are running OS X. I'm using xbuild to run MSBuild scripts on Mono. The website can be compiled without much problems. However, I'm unable to find how the equivalent of aspnet_compiler.exe on Mono. I cannot find the AspNetCompiler build task and google searches return [a stub implementation] from a long time ago. Does the AspNetCompiler task exist in Mono? Are there alternatives for compiling an ASP

Configure Visual Studio 2013 to allow ASPNETCOMPILER to precompile using the x64 compiler

扶醉桌前 提交于 2019-12-04 13:03:04
问题 How can I use the "Precompile during publishing" flag on a VS2013 x64 project? No matter what I do, it fails to publish because it insists on using the x86 ASPNETCOMPILER. I think I used to have this working in VS2012, but after upgrading to VS2013 it is no longer working. I recall the fix involving changing a text file related to MSBuild but I honestly don't know very much about it so it's a little hazy. Any help is greatly appreciated. Thanks! 回答1: This seems to be a bug in Visual Studio

Unable to publish using msbuild or aspnet_compiler using cc.net

烂漫一生 提交于 2019-12-04 12:04:56
I am trying to automate publishing a project having many solutions in cc.net. I am using msbuild which in turn calls a aspnetcompiler xml file. Problem is my directory contains many solutions and when I run aspnetcompiler it gives me the following error. errorASPCONFIG: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS I have tried all possible solutions given at many forums. But I am confused how to explicitly tell aspnet_compiler to

Howto Force TFS 2010 to build a website using the 32bit ASPNET Compiler on a 64 bit build machine

非 Y 不嫁゛ 提交于 2019-12-04 04:02:23
问题 We have a very large product that compiles just fine on our 32 bit build controllers and mostly on our 64 bit build controllers with one exception. We have a precompiled web forms front end. When it builds on the 64 bit machine it shows a command line in the log file of *C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_compiler.exe -v /ourwebapp -p ..\ourwebapp\ -u -f "........\Binaries\Mixed Platforms_PublishedWebsites\ourwebapp\"* This causes an error because of some 32 bit third part

Visual Studio 2013 calls 32 bit aspnet_compiler instead of 64 bit one

自古美人都是妖i 提交于 2019-12-04 02:48:19
My solution contains some .net projects and one of them is a ASP.NET MVC project, which I'm trying to publish. All configurations are set correctly, x32 and x64, non of them is set to AnyCPU. Problem: If I try to publish the project as 32bit, everything is fine, but trying to publish in 64 bit mode fails with an error: Could not load file or assembly "ProjectA" or one of its dependencies. An attempt was made to load a program with an incorrect format. What I've tried and noticed: Since VS 2013, MSbuild is a part of VS and not of .NET Framework as before. If I simply build the solution in x64

ASP.NET in-place precompile doesn’t work as expected

时间秒杀一切 提交于 2019-12-03 09:49:39
I am trying to use ASP.NET precompile tool aspnet_compiler.exe to compile site after it has been deployed. As per book definition running in-place precompile on web machine should improve first page load experience. The compilation tool compiles each ASP.NET page, storing the compiled version in the %WINDIR%\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files folder just like if the pages had each been visited for the first time from a browser. In-place precompilation can speed up the first request made to newly deployed ASP.NET pages on your site because it alleviates the runtime from

Howto Force TFS 2010 to build a website using the 32bit ASPNET Compiler on a 64 bit build machine

前提是你 提交于 2019-12-02 00:01:26
We have a very large product that compiles just fine on our 32 bit build controllers and mostly on our 64 bit build controllers with one exception. We have a precompiled web forms front end. When it builds on the 64 bit machine it shows a command line in the log file of *C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_compiler.exe -v /ourwebapp -p ..\ourwebapp\ -u -f "........\Binaries\Mixed Platforms_PublishedWebsites\ourwebapp\"* This causes an error because of some 32 bit third part dll's we have: ASPNETCOMPILER : error ASPCONFIG: Could not load file or assembly 'Leadtools.Codecs' or

Trying to Build and Publish Asp.net website from command line using aspnet_compiler

北慕城南 提交于 2019-12-01 21:24:57
问题 I am trying this. I have built asp.net website. When I publish to IIS through VS2008 it works fine. Lets say my site is at c:\projects\Website1\ I want to publish it to c:\Inetpub\wwwroot\WebsiteOne I am trying to mimic publish from studio. That is publish and remove anything that is in side. I tried this: aspnet_compiler -v/WebsiteOne -f c:\Inetpub\wwwroot\WebsiteOne Error: error ASPRUNTIME: The precompilation target directory (c:\Inetpub\wwwroot\WebsiteOne) cannot be in the same tree as the

Trying to Build and Publish Asp.net website from command line using aspnet_compiler

非 Y 不嫁゛ 提交于 2019-12-01 19:47:37
I am trying this. I have built asp.net website. When I publish to IIS through VS2008 it works fine. Lets say my site is at c:\projects\Website1\ I want to publish it to c:\Inetpub\wwwroot\WebsiteOne I am trying to mimic publish from studio. That is publish and remove anything that is in side. I tried this: aspnet_compiler -v/WebsiteOne -f c:\Inetpub\wwwroot\WebsiteOne Error: error ASPRUNTIME: The precompilation target directory (c:\Inetpub\wwwroot\WebsiteOne) cannot be in the same tree as the source application directory (c:\inetpub\wwwroot\WebsiteOne). When I tried this: aspnet_compiler -v

Circular file references not allowed

╄→гoц情女王★ 提交于 2019-11-29 09:12:06
I am having a problem in building my solution in VS2008. Normally, it compiles fine in the environment. Sometimes, it fails with: /xxx_WEB/secure/CMSManagedTargetPage.aspx(1): error ASPPARSE: Circular file references are not allowed. I rebuild and it works fine. Now, however, I am in the middle of setting up a CruiseControl.NET system and am testing my checked out code with MSBuild before I integrate the build into CC. Now, everytime I MSBuild, I get: "Q:\cc\xxx\checked out from svn\xxx.sln" (default target) (1) -> (xxx_WEB target) -> /xxx_WEB/secure/CMSManagedTargetPage.aspx(1): error