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

Enable Code Analysis #63

Open
smudge202 opened this issue May 20, 2015 · 7 comments
Open

Enable Code Analysis #63

smudge202 opened this issue May 20, 2015 · 7 comments

Comments

@smudge202
Copy link
Collaborator

Compose doesn't conform to CA

@smudge202 smudge202 added the bug label May 20, 2015
@smudge202 smudge202 added this to the 0.1.4-beta milestone May 20, 2015
@smudge202 smudge202 modified the milestones: 0.1.5-beta, 0.1.4-beta Jun 2, 2015
@smudge202
Copy link
Collaborator Author

Moving this back to v0.1.5-beta because it does not block ongoing development of consumer software.

@ghost
Copy link

ghost commented Jun 2, 2015

I can take a look at in the next few days when I feel a bit better. Just lettme know which branch to fork from

@smudge202
Copy link
Collaborator Author

dev

@smudge202 smudge202 assigned ghost Jun 19, 2015
@smudge202 smudge202 unassigned ghost Jun 30, 2015
@smudge202
Copy link
Collaborator Author

Be worth investigating whether this is an sdk package or an analysis package: https://www.nuget.org/packages/Microsoft.CodeAnalysis/1.0.0-rc3

@ghost
Copy link

ghost commented Jul 2, 2015

This might be what we actually want: https://github.com/DotNetAnalyzers/StyleCopAnalyzers - more research to come later. Depends on what level of CA is required, probably best to discuss that first. //cc @mattridgway

@ghost
Copy link

ghost commented Jul 5, 2015

Progress update:

I believe the correct package is actually Microsoft.CodeAnalysis.Analyzers. In order to get them to run properly on my machine, I had to create a seperate project and pull in the same code. That said, I have some type load exceptions from one or more of the analysers. For the ones that it did manage to do, we just need to mark the Exceptions are serializable. I've not actioned this yet as we still have the pending discussion: https://github.com/4Com/compose-remoting/issues/18

@smudge202 smudge202 modified the milestones: later, 0.1.5-beta Jul 22, 2015
@herecydev
Copy link
Contributor

In the latest ASP.NET community standup there was some talk about code analysis coming in the future. They've obviously got plans about how they want it. Right now it's a bit of a mess; different authors producing lots of packages. Not sure what the "correct" way of doing things is.

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

2 participants