SQL Code Guard v2.8 released

Main change - SCG moved back to .Net framework 3.0 to restore support of SSMS 2008/2008R2
Few small fixes, additional logging, nothing critical.
Enjoy!

Using SQL Code Guard TFS Checkin Policy with VS2013

To use TFS Checking policy the first thing that you must do - is to add policy to your TFS source control
The process itself is pretty simple

1. Install SQL Code Guard at target computer. Please remember that you will need to have SCG installed on each computer on which you will do checkin to project with SCG policy enabled.
2. Register SQL Code Guard with VS - devenv /setup

1. add checking policy
1. select TFS collection / project
2. open menu TEAM -> Team Project Settings -> Source Control
3. Select Check-in Policy tab
4. click Add button
5. select SQLCodeGuard.CheckinPolicy policy and press OK button
6. Press OK to close "Source control settings" dialog

Now you can try to use/test checkin policy

1. add (or edit) sql file in TFS
2. select "Pending changes"
3. If you didnt placed SQL Code Guard settings file in project directory then you will get message "Unable to find settings"
4. if there are issues in script file - you will see warning message

You can doubleclick on message and error list window with full set of of issues will appear

Doubleclick on issue will navigate you to location of issue.

That's all, folks!

24HOP Russian Edition

Spoke at 24HOP Russian edition.
Interesting experience.
It is difficult to determine mood of audience if there is no visible audience  :)
And looks like that 90 minutes is too less for me.

SQL Code Guard v2.7 and SQL Server 2008R2: bad news and good news

Hi all!
Bad news: SQL Code Guard v2.7 is not working with SSMS from SQL Server 2008R2 (and below).
Good news: I know about this issue, already fixed it in my development environment and will release fix in nearest possible future.
Bad news (again) : integration will not work with SSMS from SQL Server 2005. Even in next release.

SQL Code Guard v2.7 released

Hola!
SqlCodeGuard v2.7 is just released.

To be brief - major changes:

1. Added command line utility
2. Added scgallow(issue)/scgignore(issue`)to control which issues should be registered
3. Added [SC004] Found todo item. You can use "--# todo <text>", "--# bug <text>", "--# fix <text>" or "--# warning <text>" marks in your scripts.
4. Added support for VS2013
5. SQL Code Guard moved to .Net Framework 4.0

Full list of changes can be found here 

Bon appétit!

ExpressProfiler - new build published

Just published new signed build of ExpressProfiler - few nice improvements like advanced search, stay on top window, transparency - just to make life easier
Actually there is no change since last august, i simply build, sign and publish version that already was in CodePlex's TFS, but now you can get binaries.

How to fix: Visual Studio 2012 startup problem: The 'HDIProjectPackage' package did not load correctly.

After installing Community Edition of VS2013 with some additional packages i've noticed that my VS2012 starts failing to start with message like "The 'HDIProjectPackage' package did not load correctly. The problem may have been caused by a configuration change or by the installation of another extension. You can get more information by examining the file 'C:\Users\************\AppData\Roaming\Microsoft\VisualStudio\11.0\ActivityLog.xml'."

Activity log shows

SetSite failed for package [HDIProjectPackage]
End package load [HDIProjectPackage]
{665BA479-E656-4485-9097-7CE2A22A90F2} (just to let Google to find this page)

Google knows nothing about HDIProjectPackage. I dont know how to fix errors with VS2012. I'm stuck!
After 24 hours of thinking and meditation (and several reinstalls of both VS2012 and VS2013) I've found that the problem was with "Microsoft Azure HDInsight Tools for Visual Studio" which I've installed via Web Platform Installer
HDIProjectPackage->HDInsight, looks similar, right?
So I uninstalled "Microsoft Azure HDInsight Tools for Visual Studio" and my VS2012 now alive!!!!!
And I can continue to develop next release of SqlCodeGuard with such nice features like, say, preprocessor commands to disable specific issues in particular scripts (or even - part of script)