Skip to content
This repository was archived by the owner on Dec 14, 2018. It is now read-only.

Get builds working better within VS (temporary fix?); disable pre-compilation #2499

Closed
wants to merge 1 commit into from

Conversation

dougbu
Copy link
Member

@dougbu dougbu commented May 4, 2015

…pilation

- remove `RazorPreCompilation.cs` files from all but the PrecompilationWebSite
- related to #2498 but not addressing that issue since pre-compilation is what that site is about
@ghost ghost added the cla-already-signed label May 4, 2015
@dougbu
Copy link
Member Author

dougbu commented May 4, 2015

@Eilon @rynowak @pranavkm any thoughts on doing this until and unless we get pre-compilation working reliably when building functional tests within VS?

@rynowak
Copy link
Member

rynowak commented May 5, 2015

I'd want to have @Eilon 's ok, but to me anything that's blocking developer workflow needs to be addressed.

Are you seeing any issues other than errors in VS?

@dougbu
Copy link
Member Author

dougbu commented May 5, 2015

No other issues. In fact VS freezes more often when I'm editing in the Razor repo 😦

Note this leaves the #2498 errors in play. I could remove those 10 as well. But then we might as well throw away the PrecompilationWebSite entirely.

@Eilon
Copy link
Member

Eilon commented May 5, 2015

  1. Is this a tooling bug? Runtime bug? Where is the underlying bug logged?
  2. I'm ok checking this in, but also log a bug to restore these (including pointing to the changeset that removes these)

@dougbu
Copy link
Member Author

dougbu commented May 5, 2015

@Eilon

  1. I looked at PrecompilationWebSite has troubles building in VS #2498 some without narrowing the problem down much. The symptoms certainly point toward a component used only when pulling the PrecompilationWebSite into a larger VS build (but I can't think of a component unique to that scenario) or some lack of generality in the site itself, the functional test setup, VS, or the runtime. So, yeah, it's one of the bits you listed 😄 and right now PrecompilationWebSite has troubles building in VS #2498 is filed in MVC.
  2. Sure. Will file after I push.

In the meantime I'll add the additional errors seen without this change to the commit description. That is, I'll make sure the change still makes a difference a few days later.

@Eilon
Copy link
Member

Eilon commented May 5, 2015

@dougbu ok thanks go ahead and merge.

@dnfclas
Copy link

dnfclas commented May 6, 2015

@dougbu, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.

Thanks, DNFBOT;

@rynowak
Copy link
Member

rynowak commented May 8, 2015

@dougbu should this be closed?

@dougbu
Copy link
Member Author

dougbu commented May 8, 2015

@rynowak I didn't get back to this over the last couple of days. The change definitely makes debugging Razor code-generation orders of magnitude easier. I'll try to reproduce the original issue(s) over the weekend and re-confirm the change helps even when not doing low-level debugging.

Will take a more definitive action in the next day or two...

@dougbu
Copy link
Member Author

dougbu commented May 11, 2015

Checked VS behaviour without this change. Much uglier -- 26 errors instead of the 10 (mentioned in #2498) just for PrecompilationWebSite. And I can't start the tag helper sample from VS.

So I'll check this change in shortly.

@dougbu
Copy link
Member Author

dougbu commented May 11, 2015

3fbead0

@dougbu dougbu closed this May 11, 2015
@dougbu
Copy link
Member Author

dougbu commented May 11, 2015

@Eilon w.r.t.

also log a bug to restore these (including pointing to the changeset that removes these)

I added a link to the commit in the existing #2498 which is generally about Razor precompilation issues.

@dougbu dougbu deleted the dougbu/temporary.fix branch May 20, 2015 21:07
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants