clraddins Release Rss Feed

Reviewed: Add-in FxCop Rules - v1.0 beta (Feb 18, 2009)

orin_chen — Thu, 19 Feb 2009 06:30:43 GMT

Rated 4 Stars (out of 5) - Good

UPDATED RELEASE: Add-in FxCop Rules - v1.0 beta (Jul 03, 2008)

Mon, 07 Jul 2008 23:12:43 GMT

This is the first release of the Add-in FxCop Rules

To build the solution:

Install FxCop v1.35: http://code.msdn.microsoft.com/codeanalysis/Release/ProjectReleases.aspx?ReleaseId=553
Download and extract AddInFxCopRules.zip below. Open the solution in Visual Studio.
Add references in both projects to the FxCop assemblies FxCopSdk.dll and Microsoft.Cci.dll. These are located within the "Microsoft FxCop 1.35" folder under Program Files.

To run the rules against your contract and view assemblies:

Install FxCop v1.35: http://code.msdn.microsoft.com/codeanalysis/Release/ProjectReleases.aspx?ReleaseId=553
Launch FxCop from the Start Menu. If it prompts you to update to FxCop 1.36 beta, click "No". This is because we have built and tested the rules against FxCop 1.35.
In FxCop menu, click Project/Add Targets. Select the view or contract assembly to run checks against.
In FxCop menu, click Project/Add Rules. Navigate to the AddInFxCopRules\bin folder and select either Microsoft.AddIn.FxCopRules.ContractRules.dll or Microsoft.AddIn.FxCopRules.ViewRules.dll, depending on which assembly you want to scan. If you want to run only the AddIn rules, you can uncheck the built-in FxCop rules in the "Rules" tab.
Click Analyze, and FxCop will scan the assemblies and list any rule violations detected.

The rules can also be run from command-line using fxcopcmd.exe in the FxCop folder. Thus they can be integrated into build processes and run automatically.

Let us know how this works out! We would love to hear your feedback.

Released: Add-in FxCop Rules - v1.0 beta (Jul 03, 2008)

Mon, 07 Jul 2008 23:12:43 GMT

This is the first release of the Add-in FxCop Rules

To build the solution:

Install FxCop v1.35: http://code.msdn.microsoft.com/codeanalysis/Release/ProjectReleases.aspx?ReleaseId=553
Download and extract AddInFxCopRules.zip below. Open the solution in Visual Studio.
Add references in both projects to the FxCop assemblies FxCopSdk.dll and Microsoft.Cci.dll. These are located within the "Microsoft FxCop 1.35" folder under Program Files.

To run the rules against your contract and view assemblies:

Install FxCop v1.35: http://code.msdn.microsoft.com/codeanalysis/Release/ProjectReleases.aspx?ReleaseId=553
Launch FxCop from the Start Menu. If it prompts you to update to FxCop 1.36 beta, click "No". This is because we have built and tested the rules against FxCop 1.35.
In FxCop menu, click Project/Add Targets. Select the view or contract assembly to run checks against.
In FxCop menu, click Project/Add Rules. Navigate to the AddInFxCopRules\bin folder and select either Microsoft.AddIn.FxCopRules.ContractRules.dll or Microsoft.AddIn.FxCopRules.ViewRules.dll, depending on which assembly you want to scan. If you want to run only the AddIn rules, you can uncheck the built-in FxCop rules in the "Rules" tab.
Click Analyze, and FxCop will scan the assemblies and list any rule violations detected.

UPDATED RELEASE: Add-in FxCop Rules - v1.0 beta (Jul 03, 2008)

Thu, 03 Jul 2008 19:21:34 GMT

This is the first release of the Add-in FxCop Rules

To build the solution:
#Install FxCop v1.35: http://code.msdn.microsoft.com/codeanalysis/Release/ProjectReleases.aspx?ReleaseId=553
#Download and extract AddInFxCopRules.zip below. Open the solution in Visual Studio.
#Add references in both projects to the FxCop assemblies FxCopSdk.dll and Microsoft.Cci.dll. These are located within the "Microsoft FxCop 1.35" folder under Program Files.

To run the rules against your contract and view assemblies:
#Install FxCop v1.35: http://code.msdn.microsoft.com/codeanalysis/Release/ProjectReleases.aspx?ReleaseId=553
#Launch FxCop from the Start Menu. If it prompts you to update to FxCop 1.36 beta, click "No". This is because we have built and tested the rules against FxCop 1.35.
#In FxCop menu, click Project/Add Targets. Select the view or contract assembly to run checks against.
#In FxCop menu, click Project/Add Rules. Navigate to the AddInFxCopRules\bin folder and select either Microsoft.AddIn.FxCopRules.ContractRules.dll or Microsoft.AddIn.FxCopRules.ViewRules.dll, depending on which assembly you want to scan. If you want to run only the AddIn rules, you can uncheck the built-in FxCop rules in the "Rules" tab.
#Click Analyze, and FxCop will scan the assemblies and list any rule violations detected.

The rules can also be run from command-line using fxcopcmd.exe in the FxCop folder. Thus they can be integrated into build processes and run automatically.

Let us know how this works out! We would love to hear your feedback.

RELEASED: Add-in FxCop Rules - v1.0 beta (Jul 03, 2008)

Thu, 03 Jul 2008 19:21:34 GMT

UPDATED RELEASE: Pipeline Builder CTP Feb-2008 (Mar 11, 2008)

Tue, 11 Mar 2008 22:19:52 GMT

*Note: if you have a previous version of this tool installed you should unintall that version first. It will show up in Add/Remove Programs as "Visual Studio Pipeline Builder"*

This is the latest Pipeline Builder CTP.
Major Changes:
** Better VS Integration
** Greatly improved performance of the VS add-in for larger contract assemblies
** Better default naming conventions for views and adatpers
** Support for structs in Contracts

Minor Breaking Changes:
** Generated files are now placed in a "Generated Files" sub folder in the main project and with a ".g.cs" extension rather than ".generated.cs". You will need to delete the existing generated source files to compile.
** NamespaceAttribute is no longer valid on assemblies
** The namespaces for generated code has changed slightly, see [workitem:901]

For a full list of changes see [New in Feb CTP]

Please see the [Pipeline Builder] home page for more information.

Quick Samples:
** [release:Blank Pipeline Project | 9240] (Updated to include a sample contract)
** [release:Common Pipeline Scenarios | 9241] (Updated to include samples for structs)

UPDATED RELEASE: Pipeline Builder CTP March-2008 (Feb 08, 2008)

Thu, 06 Mar 2008 19:16:23 GMT

*Note: if you have a previous version of this tool installed you should unintall that version first. It will show up in Add/Remove Programs as "Visual Studio Pipeline Builder"*

This is the latest CTP of Pipeline Builder. You can find the release page for the previous version [release:here|11395]

Major Changes:
** Pipeline Builder now supports contracts with "ref" and "out" parameters

Minor Changes:
** Small bug fixes smoothing up VS integration
** Fixed bugs related to the AllowViewUpCasting attribute

This was just a minor refresh with one new feature and a few bug fixes. If you are upgrading from the Jan CTP please take a look at the [New in Feb CTP] page.

Please see the [Pipeline Builder] home page for more information.

Quick Samples:
** [release:Blank Pipeline Project | 9240]
** [release:Common Pipeline Scenarios | 9241]

UPDATED RELEASE: Sample- Cross Boundary Performance Testbed (Feb 22, 2008)

Fri, 22 Feb 2008 21:58:06 GMT

This sample demonstrate the costs of crossing different isolation boundaries using different types of calls. For more information see the detailed article on our blog: HERE

*Note:*After you build this sample you need to install the contract assembly into the gac. You can do this with the command "gacutil -if [contractPath]". If you decided to change the contract assembly you will need to re-install the new version of the assembly in the gac before your application or the Pipeline Builder tool will be able to use it.

CREATED RELEASE: Sample- Cross Boundary Performance Testbed (Feb 22, 2008)

Fri, 22 Feb 2008 21:55:29 GMT

UPDATED RELEASE: Pipeline Builder CTP Feb-2008 (Feb 08, 2008)

Sun, 17 Feb 2008 01:37:09 GMT

UPDATED RELEASE: Pipeline Builder CTP Feb-2008 (Feb 08, 2008)

Fri, 08 Feb 2008 22:48:52 GMT

This is the latest Pipeline Builder CTP.
Major Changes:
** Better VS Integration
** Greatly improved performance of the VS add-in for larger contract assemblies
** Better default naming conventions for views and adatpers
** Support for structs in Contracts

Minor Breaking Changes:
** Generated files are now placed in a "Generated Files" sub folder in the main project and with a ".g.cs" extension rather than ".generated.cs". You will need to delete the existing generated source files to compile.
** NamespaceAttribute is no longer valid on assemblies
** The namespaces for generated code has changed slightly, see [workitem:901]

For a full list of changes see [New in Feb CTP]

Please see the [Pipeline Builder] home page for more information.

Quick Samples:
** [release:Blank Pipeline Project | 9240] (Updated to include a sample contract)
** [release:Common Pipeline Scenarios | 9241] (Updated to include samples for structs)

UPDATED RELEASE: Pipeline Builder CTP Jan-2008 (Jan 17, 2008)

Fri, 08 Feb 2008 22:48:04 GMT

_*This is a legacy release maintained for convenience. You can find the latest version [release:here|9222].*_

This is the initial release of our Pipeline Builder project.

Please see the [Pipeline Builder] home page for more information.

Quick Samples:
** [release:Blank Pipeline Project | 9240]
** [release:Common Pipeline Scenarios | 9241]

UPDATED RELEASE: Pipeline Builder CTP Feb-2008 (Jan 10, 2008)

Fri, 08 Feb 2008 22:26:07 GMT

UPDATED RELEASE: Pipeline Builder CTP 1-2008

Fri, 08 Feb 2008 22:07:11 GMT

UPDATED RELEASE: Pipeline Builder CTP 1-2008

Fri, 08 Feb 2008 22:04:39 GMT

This is the initial release of our Pipeline Builder project.

Please see the [Pipeline Builder] home page for more information.

Quick Samples:
** [release:Blank Pipeline Project | 9240]
** [release:Common Pipeline Scenarios | 9241]

UPDATED RELEASE: Pipeline Builder CTP Feb-2008 (Jan 10, 2008)

Fri, 08 Feb 2008 22:02:11 GMT

This is the latest Pipeline Builder CTP.
Major Changes:
** Better VS Integration
** Better default naming conventions for views and adatpers
** Support for structs in Contracts

For a full list of changes see [New in Feb CTP]

Please see the [Pipeline Builder] home page for more information.

Quick Samples:
** [release:Blank Pipeline Project | 9240] (Updated to include a sample contract)
** [release:Common Pipeline Scenarios | 9241] (Updated to include samples for structs)

UPDATED RELEASE: Pipeline Builder CTP 1-2008 (New)

Fri, 08 Feb 2008 21:57:55 GMT

UPDATED RELEASE: Pipeline Builder CTP 1-2008 (New)

Fri, 08 Feb 2008 21:55:58 GMT

UPDATED RELEASE: Sample- Blank Pipeline Project (Jan 10, 2008)

Fri, 08 Feb 2008 21:51:23 GMT

This is an VS 2008 solution containing an empty contract project. Everything is set up so that it works well with the pipeline builder tool.

This sample pre-reqs [release:9222].

For general information on how to use the Pipeline Builder tool see this [page|Using the VS Add-In].
For information on how to use this project see this [page|From Blank Pipeline Project To Working Solution].

UPDATED RELEASE: Pipeline Builder CTP 2-2008

Fri, 08 Feb 2008 21:34:06 GMT

Please see the [Pipeline Builder] home page for more information.

Quick Samples:
** [release:Blank Pipeline Project | 9240]
** [release:Common Pipeline Scenarios | 9241]

New in this Release:
This release will fix/address many of the issues filed after the Jan CTP. In addition to fixing the issues and general polish for the VS integration piece, the main new feature is support for struct contracts.