I am new to using Gendarme. I downloaded this version of the tool (Gendarme 2.11 (unsupported build - Win32 - Requires .NET Framework 4.0)) from https://github.com/spouliot/gendarme/downloads and it worked fine as an independent app. But I want to integrate it with my VS2010 Premium. After lot of search I found that this (https://github.com/unintelligible/GendarmeMsBuild) is the only wrapper that serves my purpose. I did what has been mentioned there to integrate it with VS but I did not see any code review suggestion from the tool i.e. no output from the tool. I tried to integrate it only to VS and did not try for MSBuild yet.
What is it that I might be doing wrong? Anyone please?
I am also open to the idea of integrating Gendarme to VS and MSBuild by some other way too if it works.
Thanks in advance!
Related
Installation of NServiceBus was smooth and straightforward. No issues there.
Now, I'm trying to play with a sample solution to see what happens behind the screens. Just trying to follow instructions here - http://docs.particular.net/samples/
And I get this error when creating an endpoint.
Reinstalled the VS add-in. Restarted VS 2010. No luck.
Any ideas?
It seems like you don't have the ASP NET MVC 3 project type installed on your environment. Please try installing ASP.Net MVC from http://www.asp.net/mvc/mvc3
If you have tried to install it using the Web Platform Installer Tool, be sure that you installed the right version and product (At least for me, it's easy to pick the wrong one with so many similar named products).
I'm trying to deploy a VB.NET app which is an extension to Excel using VSTO. It works fine in the development environment, but when someone else (without a dev environment installed, just the .NET framework) installs it, they get:
The common language runtime could not be loaded by <application>. Contact your administrator for further assistance.
Google pops up the microsoft help page for this:
http://msdn.microsoft.com/en-us/library/6s0wczt9.aspx
But I've verified that the .NET versions are the same on both machines. For VSTO apps in 2k5 there was a specific vsto runtime library users needed to install -- is there something similar for VS2008 that I haven't found yet? Any ideas besides that?
Thanks in advance!
For VSTO apps built with Visual Studio 2008, The VSTO version 3.0 Runtime is required.
Here is the download page: http://www.microsoft.com/downloads/details.aspx?FamilyID=54eb3a5a-0e52-40f9-a2d1-eecd7a092dcb&DisplayLang=en
Make sure they have the correct version of the .NET framework. If they have .NET 1.1 (or even 2.0) installed, and you're targetting the 3.5 framework, you can get this error message.
We had the same problem. It's all to do with security policy.
There are issues with the security policy for your DLL's when running VSTO projects.
Namely you need to grant 'full trust' to your assemblies. What this means you have to A) sign your projects with a key, and B) register your assemblies as having full trust during deployment (which can be done easily with CASPOL.exe: http://msdn.microsoft.com/en-us/library/cb6t8dtz.aspx)
Its very easy to do. Alternatively you can roll your own security-setting assembly which you integrate into your msi (thats what we did)
Check out this MSDN Article for the full details:
http://msdn.microsoft.com/en-us/library/zdc263t0.aspx
Install VSTO runtime 3.0
Then update it to VSTO 3.0 SP1
also install VSTO_PTExtLibs.exe (PIA extension libs for runtime) if you are referencing these in your project.
I am building an executable using VS2008 and .NET compact framework 3.5, targetting Windows Mobile 6 professional, but whenever I compile the project, everything that I have specified in the AssemblyInfo.cs file is ignored.
I have done this many times in other projects and it works without problem, but for some reason I cannot get the AssemblyTitle/AssemblyProduct/AssemblyVersion attributes etc to show up (I am trying to view them using Windows Explorer, I am able to see these properties in the details tab for any other assembly that I have built - even other projects in the same solution).
Any suggestions?
That info is looking at the native version info, which on the desktop is set using the AssemblyFileVersionAttribute. The AssemblyFileVersionAttribute is unsupported in the CF, so the only way to set the version info out of the box is to command-line compile. There is a workaround in this blog.
I know this is old, but there's a simpler solution posted here:
Version number in .NET Compact Framework application
You have to use reflection.
System.Reflection.Assembly.GetExecutingAssembly().GetName().Version.Major System.Reflection.Assembly.GetExecutingAssembly().GetName().Version.Minor System.Reflection.Assembly.GetExecutingAssembly().GetName().Version.Build System.Reflection.Assembly.GetExecutingAssembly().GetName().Version.Revision
in tag PlatformFamilyName; rather that PocketPC, change to add WindowsCE
in csproj
We were using nant for building our project (10+Class Lib) and a Web Site which was based on the ASP.NET 2.0. Recently we are in the process of moving towards the ASP.NET 3.5. I searched in the net and found that nant doesn't support 3.5.
I am also looking in to option of migrating MSBuild.
Is the MS Build right candidate for this?
I heard people saying that MSBuild is slow? is it True?
With MS Build can I have a Single step build ? in nant all I will do is to call nant.ext and give a build file it will do a build and give me the output.
NAnt can easily be made to support .NET 3.5 - we use it here. Rather than claim credit, check this blog post.
Have a look at the Nant Site
.net Framework 3.5 is supported
In MsBuild you can have a single step build. Nant can be used with .Net 3.5 but is always behind the times (.Net 4.0 is soon to be shipped). Nant .86 beta1 has issues with x64 Windows Server 2003 (You will need to use a nightly build). I have used both and prefer MsBuild. For more details check out an older blog post I wrote Nant vs MsBuild
Is it possible to build a VS2008 solution (C# and VC++ projects) using the automated MSBuild built into TFS2010? When I niavely just run it, the build fails because the 2008 Solution file needs to be upgraded (and presumably so would the project files). Can I tell MSBuild 2010 to just build the 2008 files?
Does this blog post happen to work out for you? There are several ways you can get it working but just depends on your particular setup.
http://blogs.msdn.com/madhurig/archive/2009/11/25/building-vs2008-projects-with-tfs-build-2010.aspx