Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to optimize metageneration on build server #25

Open
GoogleCodeExporter opened this issue Jun 1, 2015 · 4 comments
Open

Ability to optimize metageneration on build server #25

GoogleCodeExporter opened this issue Jun 1, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

MetaCreator utilizes separate AppDomain for compilation of macroses. But is you 
run msbuild or devenv on a builder as a separate process, there are no reason 
in separate AppDomain, because this process will exit just after build, and 
releases all temporary assemblies.

consider to use special property in targets or conditional compilation symbol

Original issue reported on code.google.com by [email protected] on 26 Jun 2010 at 11:01

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 10 Feb 2011 at 6:53

  • Added labels: Priority-Low
  • Removed labels: Priority-Medium

@GoogleCodeExporter
Copy link
Author

it is done using AppDomainCurrentDomain.IsDefaultAppDomain()

Original comment by [email protected] on 16 Mar 2011 at 2:11

  • Changed state: Done

@GoogleCodeExporter
Copy link
Author

TestCase1: DevEnv design mode: log a domain name
TestCase2: DevEnv build mode: log a domain name
TestCase3: msbuild: log a domain name


Original comment by [email protected] on 3 Oct 2011 at 10:38

  • Changed state: InProgress

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 3 Oct 2011 at 10:39

  • Added labels: Milestone-Release1.7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant