Skip to content

Created Targets file for compilation of xaml controls in same project#9

Merged
EmptyKeys merged 3 commits intoEmptyKeys:masterfrom
aravol:master
Nov 9, 2015
Merged

Created Targets file for compilation of xaml controls in same project#9
EmptyKeys merged 3 commits intoEmptyKeys:masterfrom
aravol:master

Conversation

@aravol
Copy link
Copy Markdown
Contributor

@aravol aravol commented Oct 27, 2015

This change assumes usage as a NuGet Package. Because this is a .targets file, it will require inclusion with an existing project via addition of the following line. Note that the EmptyKeys import MUST come after the standard imoprt, or the compilation step won't be defined and the command will not execute:

<Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />
<Import Project="$(SolutionDir)packages\EmptyKeysUI_Generator.*\tools\EmptyKeys.UserInterface.targets"/>

In addition, this setup presumes that .xaml files also include in compilation their corresponding .xaml.cs files since these seem to show up in the visual tree regardless. by including these, the changes caused by recreating them will also trigger Intellisense updates

@EmptyKeys
Copy link
Copy Markdown
Owner

Thanks, I will test it out :)

EmptyKeys added a commit that referenced this pull request Nov 9, 2015
Created Targets file for compilation of xaml controls in same project
@EmptyKeys EmptyKeys merged commit 2db9bf6 into EmptyKeys:master Nov 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants