I’m not sure my questions are Umbraco specific but perhaps other Umbraco developers experienced the same issues in a similar scenario or there is some documentation about this that I missed.
I’ve a question regarding the configuration of Visual Studio code analysis with Umbraco. We have a Visual Studio project version 4.5.2. with Umbraco.Code 7.7 and ModelsBuilder.Api 3.0.6. I’ve updated the default Microsoft.CodeAnalysis.Analyzers which was shipped with the Umbraco installation to version 1.1. The website works but we are suppressing some errors which we prefer not to, hopefully someone can point me in the right direction.
The Umbraco libraries aren’t signed, when we enable signing in our project an error will be thrown that references assemblies should have a strong name? Is there a way to fix this issue properly instead of singing the libraries myself?
The models builder creates generated classes which is awesome, however they aren’t conform our rulesets. Is there a way to exclude those files from being validated? Now we are suppressing validation error 1591 and added a lot of suppressions in the GlobalSuppressions.
for #2, if you setup models builder to create the files in a separate project, you can turn off validation for that project in the projects properties.
Can you describe a little more of what you mean by "if we enable signing"?
Right now we are placing the models builder in a separate project, I was wondering if there is another solution for it. It feels more like a work around than a proper solution.
Normally we sign our libraries, in VS this can be done via Project --> Properties --> Signing --> Sign the assembly checkbox.
Visual Studio code analysis with Umbraco
I’m not sure my questions are Umbraco specific but perhaps other Umbraco developers experienced the same issues in a similar scenario or there is some documentation about this that I missed.
I’ve a question regarding the configuration of Visual Studio code analysis with Umbraco. We have a Visual Studio project version 4.5.2. with Umbraco.Code 7.7 and ModelsBuilder.Api 3.0.6. I’ve updated the default Microsoft.CodeAnalysis.Analyzers which was shipped with the Umbraco installation to version 1.1. The website works but we are suppressing some errors which we prefer not to, hopefully someone can point me in the right direction.
The Umbraco libraries aren’t signed, when we enable signing in our project an error will be thrown that references assemblies should have a strong name? Is there a way to fix this issue properly instead of singing the libraries myself?
The models builder creates generated classes which is awesome, however they aren’t conform our rulesets. Is there a way to exclude those files from being validated? Now we are suppressing validation error 1591 and added a lot of suppressions in the GlobalSuppressions.
Thanks! Martin
for #2, if you setup models builder to create the files in a separate project, you can turn off validation for that project in the projects properties.
Can you describe a little more of what you mean by "if we enable signing"?
Thanks for the reply.
Right now we are placing the models builder in a separate project, I was wondering if there is another solution for it. It feels more like a work around than a proper solution.
Normally we sign our libraries, in VS this can be done via Project --> Properties --> Signing --> Sign the assembly checkbox.
is working on a reply...