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.

Sign up for GitHub

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

Jump to bottom

Add psake to build the solution #5

Closed
gep13 opened this issue Mar 12, 2015 · 0 comments
Closed

Add psake to build the solution #5

gep13 opened this issue Mar 12, 2015 · 0 comments
Assignees
@gep13
Labels
Improvement
Milestone
0.1.0

Comments

@gep13
Copy link
Member

gep13 commented Mar 12, 2015

No description provided.

@gep13 gep13 modified the milestone: 0.1.0 Mar 12, 2015
gep13 added a commit that referenced this issue Mar 12, 2015
@gep13
(GH-5) Working on adding psake to build process
d96baac 
- Added back in Costura Fody Plugin
- Added necessary tool, i.e. NuGet and psake
- Added missing AssemblyInfo
- Added buildscripts, and xsl files, for dupfinder and inspectcode
gep13 added a commit that referenced this issue Mar 12, 2015
@gep13
(GH-5) Correcting build errors
47800c2
gep13 pushed a commit that referenced this issue Mar 12, 2015
@gep13
(GH-5) Boom! FxCop re-enabled on all projects
c3e3d7c 
- Turns out, naming the output GitHubReleaseNotes.dll and
GitHubReleaseNotes.exe, causes bad things to happen to FxCop.
- Renamed output artifacts, and fixed remaining FxCop erros
@gep13 gep13 closed this as completed Mar 12, 2015
@gep13 gep13 self-assigned this Mar 13, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gep13 gep13

Labels
Improvement
Projects
None yet
Milestone
0.1.0
Development

No branches or pull requests
1 participant
@gep13