aspnet-compiler

aspnet_compiler incremental precompile

心不动则不痛 提交于 2019-12-11 13:36:20
问题 I have a website project and I want to make aspnet_compiler precompile incrementally (right now it cleans out everything and recompile everything from scratch) I tried to delete the -f flag, and use fixednames, but then it gave me this error error ASPRUNTIME: The target directory is not empty. am I suppose to delete the target directory after each instance of precompiling? 来源: https://stackoverflow.com/questions/23644017/aspnet-compiler-incremental-precompile

How to exclude path from precompilation for AspNetCompiler in csproj

吃可爱长大的小学妹 提交于 2019-12-10 16:17:47
问题 example on command line that i use to exclude Admin path with -x C:\Users\Test>C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_compiler.exe -v /Application.Web -p D:\Application.Web -x /Application.Web/Admin after run this result is fine. But when i translate to csproj scripts. from lib https://msdn.microsoft.com/en-us/library/ms164291.aspx It does not parameter to exclude path from precompilation. Currently command on csproj file <Target Name="MvcBuildViews" AfterTargets="AfterBuild"

What is the advantage of the ASP.NET precompilation?

 ̄綄美尐妖づ 提交于 2019-12-10 14:58:18
问题 How useful is it to use Aspnet_compiler.exe instead of conventional Publish via Visual Studio? And what about resource (resx) files? 回答1: Precompilation, as opposed to simple xcopy gives you two main advantages: The filesystem will not have all the code in .aspx files and all the code behind is compiled into an assembly. There is no ASP.NET compilation delay the first time you visit a page after the server starts up. Having said that, my precompilation knowledge is a bit rusty these days,

Why do I need VirtualPath property for AspNetCompiler task

假装没事ソ 提交于 2019-12-10 12:44:08
问题 I'm trying to write a build system for a website so that I can do a one click build. I'm getting a clean copy of the code from the source code repository and then using msbuild to run a AspNetCompiler task to do all the precompile for the website. The thing that is confusing me is that I need to specify a VirtualPath or MetabasePath. I don't have a metabase path - I want to just compile it into a local directory that can then be deployed to whatever servers are chosen (ie dev servers first

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

寵の児 提交于 2019-12-09 07:41:19
问题 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

msbuild ASPNETCOMPILER ASPNETRUNTIME startIndex error

ぃ、小莉子 提交于 2019-12-08 17:41:52
问题 I have a web project that builds fine on Windows 7 with no error. When I upgraded to Windows 8, compiling the project into a compiled website throws an error. Compiling from the csproj file (not creating a website) works fine. This is the actual error that is thrown by msbuild ASPNETCOMPILER : error ASPRUNTIME: startIndex cannot be larger than length of string. [mycsproj.file.here] The line that msbuild is running that is throwing the error is C:\Windows\Microsoft.NET\Framework\v4.0.30319

How can I compile a C# solution without involving Visual Studio?

天涯浪子 提交于 2019-12-08 13:26:43
问题 I'm someone who does not particularly like Visual Studio at all and would much, much rather use my highly configured gvim to edit code than be fenced into an IDE. As such, I'm aiming for a way to compile C# code for web applications without the need of a bloated >2gb monstrosity that I will only ever need to use occasionally. Currently, I can compile existing code with the following batch script: http://www.codeproject.com/Questions/495608/howplustopluspublishplussiteplususingplusaspnet_co

Why does this call to aspnet_compiler not produce new .NET assemblies?

送分小仙女□ 提交于 2019-12-08 06:41:07
问题 I'm trying to make Visual Studio precompile my ASP.NET application that will be deployed on Azure. I've added the following to my .csproj file: <Target Name="AfterBuild"> <Message Text="Starting AspNetCompiler for $(ProjectDir)" Importance="high" /> <AspNetCompiler VirtualPath="/" PhysicalPath="$(ProjectDir)" /> </Target> Now when I ask Visual Studio to prepare a service package the following appears in the build output: Starting AspNetCompiler for [PathToMyProject] C:\Windows\Microsoft.NET

Unable to publish using msbuild or aspnet_compiler using cc.net

夙愿已清 提交于 2019-12-06 09:05:26
问题 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

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

柔情痞子 提交于 2019-12-05 20:00:20
问题 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