Razor Generator

New Post: UsePhysicalViewsIfNewer Not Working?

davidebbo — Wed, 22 May 2013 17:39:16 GMT

The project sets UsePhysicalViewsIfNewer only if running locally (see here. So it should find updated views at runtime only in the local case.

New Post: UsePhysicalViewsIfNewer Not Working?

jgd12345 — Wed, 22 May 2013 11:56:09 GMT

What does UsePhysicalViewsIfNewer do?

I downloaded the project at https://github.com/davidebbo/MvcApplicationRazorGeneratorSeparateLibrary to have a little play around. I assumed whenever I changed one of the views I wouldn't need to rebuild the project. However when I change the Home View and click refresh nothing happens until I do a rebuild.

I'd appreciate it if someone could clear this up for me. Thanks

New Post: compilation issue

brianAckermann — Tue, 21 May 2013 17:08:01 GMT

Well, I've gotten a little deeper with this issue. It turns out that whats dying is my unit test library. If I comment that out of my csproj (post build event), and from my buildDeploy.cmd script, the actual application builds just fine with RazorGenerator.

I'll take a peek at the config for the unittest project, and report back.

One thing is particularly confusing to me still, though. if I have configuration issues, shouldn't it fail to build in my development environment also? I'm confused how it builds with identical configuration in one place, but fails on another one.

Also, because I'm not the person who does the builds, I have to schedule time with them to attempt another build, so the availability for that kind of thing is a bit spotty....(just to explain any delays)

Thanks again for your attention and suggestions.

New Post: Problem when trying to use precompiled views in a separate library

JacobWagner — Tue, 21 May 2013 15:16:21 GMT

ok, this has got to be some kind of race condition having to do with the server starting up.

I recreated both apps from scratch just as I described in my last post. I discovered several things:

If I simply stop and run it again, the code runs correctly, as in my last post
If I stop the site in the ASP.Net development server, from the system tray; then the error reoccurs, but only the first time
If I force it to recompile MyPrecompiledViews but leave the server running, the error does not reoccur
If I stop the site but place a breakpoint at the beginning of RazorGeneratorMvcStart.Start then continue after the breakpoint is hit; then the error does NOT reoccur
If I switch to using IIS Express instead of the ASP.NET Development Server, the error does not occur and cannot be reproduced
If I switch back to ASP.NET Development Server (without recreating the project), the problem does not occur and cannot be reproduced

Armed with this odd set of facts I will see if I can get it working in my real site.

Jacob

New Post: Problem when trying to use precompiled views in a separate library

JacobWagner — Tue, 21 May 2013 14:48:43 GMT

It worked when I originally tested this concept, before I tried to incorporate it into my real site.

However, I went back to the basics at http://blog.davidebbo.com/2011/06/precompile-your-mvc-views-using.html and created two projects as described. I used the Internet Application template for the "main" project and the Empty template for the library, both under MVC4.

I got the error described in the original post in this thread.

---- instant update

As I was typing the above, for no reason I ran it again and IT WORKED. I made no changes. The debugger was stopped on Line 15 as described and I hit stop, then I ran it again and it worked.

I don't understand, I am going to delete the projects and start again, to see if this happens again. I will post my results here.

Jacob

New Post: Problem when trying to use precompiled views in a separate library

davidebbo — Tue, 21 May 2013 01:35:03 GMT

Looking through this thread, it has evolved through various different issues, so I'm not actually sure which one you're referring to here. :)

Are you able to get at that issue starting from a new Mvc app to which you add RG.Mvc? It would be good to isolate what may be different about your app. If you have a repro you can share (e.g. in github), that would be ideal.

New Post: Problem when trying to use precompiled views in a separate library

JacobWagner — Mon, 20 May 2013 22:09:03 GMT

I am not sure what you mean by missing the redirect. I do know that my assemblyBinding tag matches what is recommended three posts above this.

Since my last post I actually copied my app, changed the name, added it to my sln, and set the copy up as a view library. As soon as I added a reference to it I got the error. I am certain that all of the references and config files are identical except the reference to RazorGenerator.Mvc.

Jacob

P.S. thank you for responding so quickly.

New Post: Problem when trying to use precompiled views in a separate library

davidebbo — Mon, 20 May 2013 22:01:05 GMT

And are you sure that you're not missing the MVC4 binding redirect in web.config? With a binding redirect, it's should be impossible for both to be loaded.

New Post: Problem when trying to use precompiled views in a separate library

JacobWagner — Mon, 20 May 2013 21:54:13 GMT

When I create two fresh MVC4 apps and follow this procedure for them they work perfectly.

However, when I attempt to create a reference to the library from my existing app (the one I want to move a view from) it gives me the above error.

I have checked both the framework and MVC versions and they match.

When I examine "ViewEngines" in the debugger I get the message "The type 'System.Web.Mvc.ViewEngines' exists in both 'System.Web.Mvc.dll' and 'System.Web.Mvc.dll'"

I am not sure what else to do. I guess I can recreate everything, but that would be a lot of work.

Jacob

New Post: compilation issue

pranavkm — Mon, 20 May 2013 20:48:16 GMT

1) Could you try uninstalling the RazorGenerator.Mvc package and see if you are able to compile your project?
2) Can you see if you have the System.Web.Mvc listed in your web.config?
3) How is your project referencing the Mvc 4 binary (System.Web.Mvc)?

New Post: compilation issue

davidebbo — Mon, 20 May 2013 20:37:17 GMT

In the end, there is not much magic about RazorGenerator.Mvc.dll. It's just s standard assembly that depends on Mvc 3 (like Glimpse). So when using Mvc 4, binding redirects are needed.

Not that your build error mentions not finding MVC4 at all, so maybe that's part of the problem.

New Post: compilation issue

brianAckermann — Mon, 20 May 2013 20:28:53 GMT

MVC4, and the error happens at build time.

I'm leaning on it being a problem with the RazorGenerator, because thats the only substantial change I've made to the project since the last successful compile. We've had glimpse in the project for quite some time now.

The bit thats' sending me for a loop is "AutoUnify is 'true'" ... I'm not sure what that has to do with anything, and haven't had a chance to investigate that, but so far, its my best guess as a root issue.

The other matter of concern is that on the dev machines, when running the build script (as the release builder would do, from command, not from within VS), we first do a "coreClean", then "CoreCompile"....but on the builder environment, we first see "CoreClean" and then the failing "ResolveAssemblyReferences"... why does the compiler take different paths...I confess to not being conversant in compiler mechanics, so this seems like an interesting place to look for issues.

Thanks.

New Post: compilation issue

davidebbo — Mon, 20 May 2013 19:48:01 GMT

Are you using MVC3 or MVC4? Also, is this error happening at build time or runtime? Normally, assemblies are not loaded at build time.

Note that you seem to get an identical error from Glimpse, so it's probably not something directly related to RazorGenerator. Maybe you're just missing an Mvc binding redirect.

New Post: compilation issue

brianAckermann — Mon, 20 May 2013 19:38:45 GMT

I've recently added RazorGenerator to my project, and I'd like to add my thanks for adding this (imo) much needed feature to our environment. All our devs have installed the VSIX component, and we've included the RazorGenerator.Mvc dll in our project (via nuget). All is well so long as the devs are building.

But, once we hand off the source to our 'builder', we now get compiler errors:

ResolveAssemblyReferences:
  Unified primary reference "System.Web.Mvc, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf385
6ad364e35, processorArchitecture=MSIL".
      Using this version instead of original version "3.0.0.0" in "C:\work\webstore\branches\ws_365\t
mpFlex_RenameMe\RevTrakPortal\packages\Glimpse.Mvc3.1.2.1\lib\net40\Glimpse.Mvc3.dll" because AutoUni
fy is 'true'.
      Using this version instead of original version "3.0.0.0" in "C:\work\webstore\branches\ws_365\t
mpFlex_RenameMe\RevTrakPortal\packages\RazorGenerator.Mvc.2.0.1\lib\net40\RazorGenerator.Mvc.dll" bec
ause AutoUnify is 'true'.
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1360,9): warning MSB3245: Coul
d not resolve this reference. Could not locate the assembly "System.Web.Mvc, Version=4.0.0.0, Culture
=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL". Check to make sure the assemb
ly exists on disk. If this reference is required by your code, you may get compilation errors. [C:\wo
rk\webstore\branches\ws_365\tmpFlex_RenameMe\RevTrakPortal\UnitTestLibrary\UnitTestLibrary.csproj]
          For SearchPath "C:\work\webstore\branches\ws_365\tmpFlex_RenameMe\RevTrakPortal\packages\Ra
zorGenerator.Mvc.2.0.1\lib\net40".
          Considered "C:\work\webstore\branches\ws_365\tmpFlex_RenameMe\RevTrakPortal\packages\RazorG
enerator.Mvc.2.0.1\lib\net40\System.Web.Mvc.dll", but it didn't exist.
          Considered "C:\work\webstore\branches\ws_365\tmpFlex_RenameMe\RevTrakPortal\packages\RazorG
enerator.Mvc.2.0.1\lib\net40\System.Web.Mvc.exe", but it didn't exist.

Thats just a short sample of the errors, but hopefully its enough to get things started.

What have I missed? I don't see anything in the documentation that suggests we should need to modify the main build script in any way.

FYI, the computer which performs the release build does not have VS installed on it at all, it does everything with msbuild. But, we don't want to be using a msbuild-task to perform the generation, we just want to compile what's already there.

Thanks!

New Post: RazorGenerator inside a NuGet package

davidebbo — Sat, 18 May 2013 23:39:44 GMT

The App_Start code that comes with the NuGet package is really just a convenient way to register things, but it is very much meant to be modified. That's why is brought in as source code rather than as part of an assembly. The same is generally true of all NuGet packages that bring in source code.

As such, it doesn't seem like a big deal to me to have to make some slight modifications. If you really don't want that, I suppose you could write a simple NuGet package that warps that RG.Mvc package, and then modifies it as you need.

New Post: RazorGenerator vs visual studio built in publish precompilation

stmarti — Fri, 17 May 2013 08:42:59 GMT

Fixed.

New Post: RazorGenerator vs visual studio built in publish precompilation

stmarti — Fri, 17 May 2013 06:53:04 GMT

It seems that the problem is with role startup code (RoleEntryPoint), see:
Now trying to fix...

New Post: RazorGenerator vs visual studio built in publish precompilation

stmarti — Fri, 17 May 2013 06:25:56 GMT

Not missing! (Checked azure instance deployed web.config via rdp)

New Post: RazorGenerator vs visual studio built in publish precompilation

davidebbo — Fri, 17 May 2013 06:15:12 GMT

Sounds like you're missing the binding redirect which normally comes with an MVC4 app. e.g. see here

New Post: RazorGenerator vs visual studio built in publish precompilation

stmarti — Fri, 17 May 2013 06:11:46 GMT

It seems that RazorGenerator.Mvc.Dll tries to load MVC 3.0. But I'm not using MVC 3.0 instead 4.0! What can be the problem?

Here is the fusion log:

*** Assembly Binder Log Entry (5/17/2013 @ 6:06:45 AM) ***

The operation failed.
Bind result: hr = 0x80131040. No description available.

Assembly manager loaded from: D:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Running under executable E:\base\x64\WaIISHost.exe
--- A detailed error log follows.

=== Pre-bind state information ===
LOG: User = NT AUTHORITY\SYSTEM
LOG: DisplayName = System.Web.Mvc, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
(Fully-specified)
LOG: Appbase = file:///E:/approot/bin
LOG: Initial PrivatePath = E:\approot\bin
LOG: Dynamic Base = NULL
LOG: Cache Base = NULL
LOG: AppName = RoleManager

Calling assembly : RazorGenerator.Mvc, Version=2.0.0.0, Culture=neutral, PublicKeyToken=7b26dc2a43f6a0d4.

LOG: This bind starts in default load context.
LOG: Using application configuration file: E:\base\x64\WaIISHost.exe.Config
LOG: Using host configuration file:
LOG: Using machine configuration file from D:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config.
LOG: Post-policy reference: System.Web.Mvc, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
LOG: GAC Lookup was unsuccessful.
LOG: Attempting download of new URL file:///E:/approot/bin/System.Web.Mvc.DLL.
LOG: Assembly download was successful. Attempting setup of file: E:\approot\bin\System.Web.Mvc.dll
LOG: Entering run-from-source setup phase.
LOG: Assembly Name is: System.Web.Mvc, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
WRN: Comparing the assembly name resulted in the mismatch: Major Version
ERR: The assembly reference did not match the assembly definition found.
ERR: Run-from-source setup phase failed with hr = 0x80131040.
ERR: Failed to complete setup of assembly (hr = 0x80131040). Probing terminated.