specsharp Wiki & Documentation Rss Feed

Updated Wiki: Documentation

alexanderjsummers — Mon, 24 Sep 2012 21:04:48 GMT

See the home page

New Comment on "Binaries"

aeterna426 — Sun, 23 Sep 2012 20:29:35 GMT

What about Spec# plugin for Visual Studio 2012 ?

New Comment on "Binaries"

mjiricka — Tue, 05 Jun 2012 20:57:28 GMT

@wuestholz: Thank you very much, you were right, I installed MSVS 2010 Premium and it works! I completely overlooked the forum. Maybe this should be written above in the steps: Spec# does not work in Express edition.

New Comment on "Binaries"

wuestholz — Sun, 03 Jun 2012 18:51:58 GMT

@mjiricka: I assume that you need VS 2010 Professional. See the following thread: http://specsharp.codeplex.com/discussions/267520.

New Comment on "Binaries"

mjiricka — Sat, 02 Jun 2012 20:59:30 GMT

I would like to try Spec#. I downloaded the latest recommended nightly build (sscboogie-nightly_rev219e6b40fa91_2012-06-02 09:01.zip), followed the steps (got three "Types registered successfully") but no new project type appeared in my MSVS Express 2010. I have Z3 in version 2.15. I have no idea what to do next... Maybe somebody can help?

New Comment on "Binaries"

mjiricka — Sat, 02 Jun 2012 20:50:11 GMT

I wanted to install the latest recommended nightly build (sscboogie-nightly_rev219e6b40fa91_2012-06-02 09:01.zip), followed the steps (got three "Types registered successfully") but no new project type appeared in my MSVS Express 2010. I have Z3 in version 4.0 but I didn't get any exception. But I guess this is completely unreletated to my installation problem. Any idea what I am doing wrong? Thanks!

New Comment on "Binaries"

EdgarPek — Fri, 03 Feb 2012 18:58:49 GMT

For installation, make sure to unblock BoogiePlugin.dll and Provers.Z3.dll, also Z3 must be 2.15 (it complained about an exception when I was using Z3 3.2).

New Comment on "Binaries"

rindPHI — Wed, 21 Dec 2011 10:07:08 GMT

Hello! I have the same issue as akku (from Jul 2 at 11:34 AM) - I'm running VS 2010 Ultimate and won't get it work. What can I do to solve the issue / contribute a usable bug report? Thanx.

Updated Wiki: Sources

rustanleino — Wed, 16 Nov 2011 02:23:12 GMT

How to install and build the sources

Install and Build for Visual Studio 2010

After downloading the sources via the "Source Code" tab, check to make sure you have any External Dependencies that you need. Then use the following directions for the program(s) you want to build. Some of them have extra dependencies. Note:

Some users have reported problems when working under cygwin due to unexpected access permissions and file ownership; we strongly recommend using the Visual Studio 2010 Command Prompt.

Spec#

Navigate to the SpecSharp\Microsoft.SpecSharp\LastKnownGood10 directory. Execute Clean.cmd and RegisterLKG.cmd. You will need to have Administrator privileges in order to execute these scripts, and you need regasm.exe on your path (you may need to right-click on the Visual Studio 2010 Command Prompt and select Run as Administrator). This registers the Spec# compiler that comes in the LastKnownGood10 directory with Visual Studio so that Spec# projects can be loaded into Visual Studio and built. Some of the projects in the compiler are Spec# projects: the compiler is partially boot-strapped. If you get errors saying that RegAsm could not load a dll, try unblocking that dll (right-click the file ==> Properties ==> Unblock).
Open up SpecSharp.sln in Visual Studio 2010 and build the "Debug" configuration (which should be selected by default). Right click on the "Checkin Tests" project and build it to make sure the regressions pass.
The previous step builds a new version of the Spec# binaries. If you want to register the new version with Visual Studio, then you should close the Visual Studio IDE, and (using a command prompt with administrator privileges) navigate to the SpecSharp\Microsoft.SpecSharp\Registration directory. Execute RegisterCurrent.cmd to register your new version with Visual Studio. If you want to deregister this version, execute the Clean.cmd script in this directory.
If your registered version of Spec# becomes unusable in VisualStudio for any reason, you can try deregistering and registering it again, by repeating (with Visual Studio closed) either step 1 (to go back to the bootstrap version) or step 3 (for your currently-compiled version) above.
Note that to run the Spec# verifier with a new version, you need to build SscBoogie, as described below.

SscBoogie (after successfully building Spec#)

Navigate to the SscBoogie\Binaries directory, and edit the definition of variable BOOGIEROOT in Makefile to point to your Boogie installation. If you didn't build into the Registration directory in the steps for building Spec# above, then you will also need to change the variable REG_DIR to point to your LastKnownGood10 directory. Then, type nmake at a command prompt (this makes local copies of various needed Spec# binaries).
In the SscBoogie\Source directory, either open SscBoogie.sln in Visual Studio and build the Debug configuration, or from a command prompt type devenv SscBoogie.sln /build Debug.
In the SscBoogie\Test directory, execute runtestall.bat. Let us know if something doesn't succeed!
Go back to the SscBoogie\Binaries directory and type nmake register at the command prompt (this copies the binaries for the verifier back to where Spec# can find them).

Install and Build for Visual Studio 2008 (not officially supported anymore)

If you have the option, we strongly recommend using Visual Studio 2010, since this is the version Spec# is currently developed and tested with. However, if you need to compile with 2008, you can follow the same instructions above, after making the following change. For each of the following three files, find the two occurrences of ";DEV10" (which should be within "DefineConstants" tags), and delete them (just the DEV10 - leave the other constants there): SpecSharp/Microsoft.VisualStudio.CodeTools/PropertyPage/PropertyPage.csproj, SpecSharp/Microsoft.VisualStudio.CodeTools/TaskManager/TaskManager.csproj, SpecSharp/Microsoft.VisualStudio.Package/Microsoft.VisualStudio.Package.csproj

Updated Wiki: Binaries

wuestholz — Thu, 13 Oct 2011 20:51:41 GMT

NOTE: if you downloaded the sources, you do not need to download the binary distribution -- the source distribution contains a bootstrapping compiler.

If you have Spec# installed from the MSR Downloads site, please uninstall it.
Go to the "Downloads" tab and click on the current release to download a zip file containing all of the binaries you need to just run Spec#.
Open a Visual Studio 2010 command prompt and navigate to the directory into which you unzipped the binaries. You will need to open that command prompt with administrator privileges (right click and select Run as Administrator).
Execute the command register.cmd. You should see three messages telling you that the types have been registered successfully. This means that Visual Studio now knows what a Spec# project is and how to build it. If you get errors saying that RegAsm could not load a dll, try unblocking that dll (right-click the file ==> Properties ==> Unblock).
If you want to run the program verifier (SscBoogie), you will also need to install Z3. We strongly recommend you to install version 2.15.
If you have Code Contracts installed (as every man, woman, and child on this planet ought), then you may get some warning dialogs when you open Visual Studio 2010 on Spec# projects. The fix is then to install Spec# before installing Code Contracts, so: uninstall Code Contracts, do the register.cmd step above, and then re-install Code Contracts.

Please let us know if something doesn't work!

Updated Wiki: Sources

wuestholz — Thu, 13 Oct 2011 20:49:33 GMT

How to install and build the sources

Install and Build for Visual Studio 2010

Some users have reported problems when working under cygwin due to unexpected access permissions and file ownership; we strongly recommend using the Visual Studio 2010 Command Prompt.

Spec#

Navigate to the SpecSharp\Microsoft.SpecSharp\LastKnownGood10 directory. Execute Clean.cmd and RegisterLKG.cmd. You will need to have Administrator privileges in order to execute these scripts, and you need regasm.exe on your path (you may need to right-click on the Visual Studio 2010 Command Prompt and select Run as Administrator). This registers the Spec# compiler that comes in the LastKnownGood10 directory with Visual Studio so that Spec# projects can be loaded into Visual Studio and built. Some of the projects in the compiler are Spec# projects: the compiler is partially boot-strapped. If you get errors saying that RegAsm could not load a dll, try unblocking that dll (right-click the file ==> Properties ==> Unblock).
Open up SpecSharp.sln in Visual Studio 2010 and build the "Debug" configuration (which should be selected by default). Right click on the "Checkin Tests" project and build it to make sure the regressions pass.
The previous step builds a new version of the Spec# binaries. If you want to register the new version with Visual Studio, then you should close the Visual Studio IDE, and (using a command prompt with administrator privileges) navigate to the SpecSharp\Microsoft.SpecSharp\Registration directory. Execute RegisterCurrent.cmd to register your new version with Visual Studio. If you want to deregister this version, execute the Clean.cmd script in this directory.
If your registered version of Spec# becomes unusable in VisualStudio for any reason, you can try deregistering and registering it again, by repeating (with Visual Studio closed) either step 1 (to go back to the bootstrap version) or step 3 (for your currently-compiled version) above.
Note that to run the Spec# verifier with a new version, you need to build SscBoogie, as described below.

SscBoogie (after successfully building Spec#)

Navigate to the SscBoogie\Binaries directory, and edit the definition of variable BOOGIEROOT in Makefile to point to your Boogie installation. Type nmake at a command prompt (this makes local copies of various needed Spec# binaries).
In the SscBoogie\Source directory, either open SscBoogie.sln in Visual Studio and build the Debug configuration, or from a command prompt type devenv SscBoogie.sln /build Debug.
In the SscBoogie\Test directory, execute runtestall.bat. Let us know if something doesn't succeed!
Go back to the SscBoogie\Binaries directory and type nmake register at the command prompt (this copies the binaries for the verifier back to where Spec# can find them).

Install and Build for Visual Studio 2008 (not officially supported anymore)

Updated Wiki: Binaries

wuestholz — Fri, 07 Oct 2011 08:34:52 GMT

NOTE: if you downloaded the sources, you do not need to download the binary distribution--the source distribution contains a bootstrapping compiler.

If you have Spec# installed from the MSR Downloads site, please uninstall it.

Go to the "Downloads" tab and click on the current release to download a zip file containing all of the binaries you need to just run Spec#.

Open a Visual Studio 2010 command prompt and navigate to the directory into which you unzipped the binaries. You will need to open that command prompt with administrator privileges (right click and select Run as Administrator).

Execute the command register.cmd. You should see three messages telling you that the types have been registered successfully. This means that Visual Studio now knows what a Spec# project is and how to build it. If you get errors saying that RegAsm could not load a dll, try unblocking that dll (right-click the file ==> Properties ==> Unblock).

If you want to run the program verifier (SscBoogie), you will also need to install Z3. We strongly recommend you to install version 2.15.

If you have Code Contracts installed (as every man, woman, and child on this planet ought), then you may get some warning dialogs when you open Visual Studio 2010 on Spec# projects. The fix is then to install Spec# before installing Code Contracts, so: uninstall Code Contracts, do the register.cmd step above, and then re-install Code Contracts.

Please let us know if something doesn't work!

Updated Wiki: External

wuestholz — Fri, 07 Oct 2011 08:11:51 GMT

External Dependencies

Spec#

Things you must have in order to build Spec#

Visual Studio 2010: Spec# is meant to be built by Visual Studio, not via makefiles. You should have at least C# and C++ installed as supported languages in Visual Studio: there are both types of projects in the Spec# solution.

SscBoogie

Things you must have in order to build SscBoogie

Spec#: SscBoogie is written in Spec#, so you need a Spec# compiler in order to build it. You can either download the Spec# binary distribution or else enlist in the Spec# CodePlex.
Boogie: SscBoogie depends on Boogie itself. If you installed the Spec# binary distribution, then you can use the Boogie binaries that come with that. Or you can get Boogie from the Boogie CodePlex project. From that site you can either install the binaries or download the sources and build it yourself.

Things you need in order to run SscBoogie

Z3: SscBoogie uses Boogie and its default is to generate verification conditions for Z3. Other theorem provers can also be used, e.g., Simplify. You will need some theorem prover that Boogie produces output for if you wish to actually find out whether a Spec# program is correct or not.

Updated Wiki: Sources

wuestholz — Fri, 07 Oct 2011 08:10:11 GMT

How to install and build the sources

Install and Build for Visual Studio 2010

Some users have reported problems when working under cygwin due to unexpected access permissions and file ownership; we strongly recommend using the Visual Studio 2010 Command Prompt.

Spec#

Navigate to the SpecSharp\Microsoft.SpecSharp\LastKnownGood10 directory. Execute Clean.cmd and RegisterLKG.cmd. You will need to have Administrator privileges in order to execute these scripts, and you need regasm.exe on your path (you may need to right-click on the Visual Studio 2010 Command Prompt and select Run as Administrator). This registers the Spec# compiler that comes in the LastKnownGood10 directory with Visual Studio so that Spec# projects can be loaded into Visual Studio and built. Some of the projects in the compiler are Spec# projects: the compiler is partially boot-strapped. If you get errors saying that RegAsm could not load a dll, try unblocking that dll (right-click the file ==> Properties ==> Unblock).

Open up SpecSharp.sln in Visual Studio 2010 and build the "Debug" configuration (which should be selected by default). Right click on the "Checkin Tests" project and build it to make sure the regressions pass (one of the regression tests fails if the language of your Windows installation is not English; just ignore that test case).

The previous step builds a new version of the Spec# binaries. If you want to register the new version with Visual Studio, then you should close the Visual Studio IDE, and (using a command prompt with administrator privileges) navigate to the SpecSharp\Microsoft.SpecSharp\Registration directory. Execute RegisterCurrent.cmd to register your new version with Visual Studio. If you want to deregister this version, execute the Clean.cmd script in this directory.

If your registered version of Spec# becomes unusable in VisualStudio for any reason, you can try deregistering and registering it again, by repeating (with Visual Studio closed) either step 1 (to go back to the bootstrap version) or step 3 (for your currently-compiled version) above.

Note that to run the Spec# verifier with a new version, you need to build SscBoogie, as described below.

SscBoogie (after successfully building Spec#)

Navigate to the SscBoogie\Binaries directory, and edit the definition of variable BOOGIEROOT in Makefile to point to your Boogie installation. Type nmake at a command prompt (this makes local copies of various needed Spec# binaries).

In the SscBoogie\Source directory, either open SscBoogie.sln in Visual Studio and build the Debug configuration, or from a command prompt type devenv SscBoogie.sln /build Debug.

In the SscBoogie\Test directory, execute runtestall.bat. Let us know if something doesn't succeed!

Go back to the SscBoogie\Binaries directory and type nmake register at the command prompt (this copies the binaries for the verifier back to where Spec# can find them).

Install and Build for Visual Studio 2008 (not officially supported anymore)

Updated Wiki: Sources

mueller — Wed, 28 Sep 2011 15:17:26 GMT

How to install and build the sources

Install and Build for Visual Studio 2010 (for 2008, see remarks below)

Some users have reported problems when working under cygwin due to unexpected access permissions and file ownership; we strongly recommend using the Visual Studio 2010 Command Prompt.

Spec#

Navigate to the SpecSharp\Microsoft.SpecSharp\LastKnownGood10 directory. Execute "Clean.cmd" and "RegisterLKG.cmd". You will need to have Administrator privileges in order to execute these scripts, and you need regasm.exe on your path (you may need to right-click on the Visual Studio 2010 Command Prompt and select Run as Administrator). This registers the Spec# compiler that comes in the LastKnownGood10 directory with Visual Studio so that Spec# projects can be loaded into Visual Studio and built. Some of the projects in the compiler are Spec# projects: the compiler is partially boot-strapped. If you get errors saying that RegAsm could not load a dll, try unblocking that dll (right-click the file ==> Properties ==> Unblock).
Open up SpecSharp10.sln in Visual Studio 2010 and build the "Debug" configuration (which should be selected by default). Right click on the "Checkin Tests" project and build it to make sure the regressions pass (one of the regression tests fails if the language of your Windows installation is not English; just ignore that test case).
The previous step builds a new version of the Spec# binaries. If you want to register the new version with Visual Studio, then you should close the Visual Studio IDE, and (using a command prompt with administrator privileges) navigate to the SpecSharp\Microsoft.SpecSharp\Registration directory. Execute "RegisterCurrent.cmd" to register your new version with Visual Studio. If you want to deregister this version, execute the "Clean.cmd" script in this directory.
If your registered version of Spec# becomes unusable in VisualStudio for any reason, you can try deregistering and registering it again, by repeating (with Visual Studio closed) either step 1 (to go back to the bootstrap version) or step 3 (for your currently-compiled version) above.
Note that to run the Spec# verifier with a new version, you need to build SscBoogie, as described below.

SscBoogie (after successfully compiling Spec#)

Navigate to the SscBoogie\Binaries directory, and edit the definition of variable BOOGIEROOT in Makefile to point to your Boogie installation. Type nmake at a command prompt (this makes local copies of various needed Spec# binaries).
In the SscBoogie\Source directory, either open SscBoogie10.sln in Visual Studio and build the Debug configuration, or from a command prompt type devenv SscBoogie10.sln /build Debug.
In the SscBoogie\Test directory, execute runtestall.bat short. Let us know if something doesn't succeed!
Go back to the SscBoogie\Binaries directory and type nmake register at the command prompt (this copies the binaries for the verifier back to where Spec# can find them).

Install and Build for Visual Studio 2008

If you have the option, we strongly recommend using Visual Studio 2010, since this is the version Spec# is currently developed and tested with. However, if you need to compile with 2008, you can follow exactly the same instructions above, after making the following change. For each of the following three files, find the two occurrences of ";DEV10" (which should be within "DefineConstants" tags), and delete them (just the DEV10 - leave the other constants there): SpecSharp/Microsoft.VisualStudio.CodeTools/PropertyPage/PropertyPage.csproj SpecSharp/Microsoft.VisualStudio.CodeTools/TaskManager/TaskManager.csproj SpecSharp/Microsoft.VisualStudio.Package/Microsoft.VisualStudio.Package.csproj

Updated Wiki: Sources

mueller — Mon, 26 Sep 2011 13:53:38 GMT

How to install and build the sources

Install and Build for Visual Studio 2010 (for 2008, see remarks below)

Some users have reported problems when working under cygwin due to unexpected access permissions and file ownership; we strongly recommend using the Visual Studio 2010 Command Prompt.

Spec#

Navigate to the SpecSharp\Microsoft.SpecSharp\LastKnownGood10 directory. Execute "Clean.cmd" and "RegisterLKG.cmd". You will need to have Administrator privileges in order to execute these scripts, and you need regasm.exe on your path (you may need to right-click on the Visual Studio 2010 Command Prompt and select Run as Administrator). This registers the Spec# compiler that comes in the LastKnownGood10 directory with Visual Studio so that Spec# projects can be loaded into Visual Studio and built. Some of the projects in the compiler are Spec# projects: the compiler is partially boot-strapped. If you get errors saying that RegAsm could not load a dll, try unblocking that dll (right-click the file ==> Properties ==> Unblock).
Open up SpecSharp10.sln in Visual Studio 2010 and build the "Debug" configuration (which should be selected by default). Right click on the "Checkin Tests" project and build it to make sure the regressions pass (one of the regression tests fails if the language of your Windows installation is not English; just ignore that test case).
The previous step builds a new version of the Spec# binaries. If you want to register the new version with Visual Studio, then you should close the Visual Studio IDE, and (using a command prompt with administrator privileges) navigate to the SpecSharp\Microsoft.SpecSharp\Registration directory. Execute "RegisterCurrent.cmd" to register your new version with Visual Studio. If you want to deregister this version, execute the "Clean.cmd" script in this directory.
If your registered version of Spec# becomes unusable in VisualStudio for any reason, you can try deregistering and registering it again, by repeating (with Visual Studio closed) either step 1 (to go back to the bootstrap version) or step 3 (for your currently-compiled version) above.
Note that to run the Spec# verifier with a new version, you need to build SscBoogie, as described below.

SscBoogie (after successfully compiling Spec#)

Navigate to the SscBoogie\Binaries directory, and edit the definition of variable BOOGIEROOT to point to your Boogie installation. Type nmake at a command prompt (this makes local copies of various needed Spec# binaries).
In the SscBoogie\Source directory, either open SscBoogie10.sln in Visual Studio and build the Debug configuration, or from a command prompt type devenv SscBoogie10.sln /build Debug.
In the SscBoogie\Test directory, execute runtestall.bat short. Let us know if something doesn't succeed!
Go back to the SscBoogie\Binaries directory and type nmake register at the command prompt (this copies the binaries for the verifier back to where Spec# can find them).

Install and Build for Visual Studio 2008

If you have the option, we strongly recommend using Visual Studio 2010, since this is the version Spec# is currently developed and tested with. However, if you need to compile with 2008, you can follow exactly the same instructions above, after making the following change. For each of the following three files, find the two occurrences of ";DEV10" (which should be within "DefineConstants" tags), and delete them (just the DEV10 - leave the other constants there): SpecSharp/Microsoft.VisualStudio.CodeTools/PropertyPage/PropertyPage.csproj SpecSharp/Microsoft.VisualStudio.CodeTools/TaskManager/TaskManager.csproj SpecSharp/Microsoft.VisualStudio.Package/Microsoft.VisualStudio.Package.csproj

Updated Wiki: Sources

mueller — Mon, 26 Sep 2011 13:51:05 GMT

How to install and build the sources

Install and Build for Visual Studio 2010 (for 2008, see remarks below)

Some users have reported problems when working under cygwin due to unexpected access permissions and file ownership; we strongly recommend using the Visual Studio 2010 Command Prompt.

Spec#

Navigate to the SpecSharp\Microsoft.SpecSharp\LastKnownGood10 directory. Execute "Clean.cmd" and "RegisterLKG.cmd". You will need to have Administrator privileges in order to execute these scripts, and you need regasm.exe on your path (you may need to right-click on the Visual Studio 2010 Command Prompt and select Run as Administrator). This registers the Spec# compiler that comes in the LastKnownGood10 directory with Visual Studio so that Spec# projects can be loaded into Visual Studio and built. Some of the projects in the compiler are Spec# projects: the compiler is partially boot-strapped. If you get errors saying that RegAsm could not load a dll, try unblocking that dll (right-click the file ==> Properties ==> Unblock).
Open up SpecSharp10.sln in Visual Studio 2010 and build the "Debug" configuration (which should be selected by default). Right click on the "Checkin Tests" project and build it to make sure the regressions pass (one of the regression tests fails if the language of your Windows installation is not English; just ignore that test case).
The previous step builds a new version of the Spec# binaries. If you want to register the new version with Visual Studio, then you should close the Visual Studio IDE, and (using a command prompt with administrator privileges) navigate to the SpecSharp\Microsoft.SpecSharp\Registration directory. Execute "RegisterCurrent.cmd" to register your new version with Visual Studio. If you want to deregister this version, execute the "Clean.cmd" script in this directory.
If your registered version of Spec# becomes unusable in VisualStudio for any reason, you can try deregistering and registering it again, by repeating (with Visual Studio closed) either step 1 (to go back to the bootstrap version) or step 3 (for your currently-compiled version) above.
Note that to run the Spec# verifier with a new version, you need to build SscBoogie, as described below.

SscBoogie (after successfully compiling Spec#)

Navigate to the SscBoogie\Binaries directory, and type nmake at a command prompt (this makes local copies of various needed Spec# binaries).
In the SscBoogie\Source directory, either open SscBoogie10.sln in Visual Studio and build the Debug configuration, or from a command prompt type devenv SscBoogie10.sln /build Debug.
In the SscBoogie\Test directory, execute runtestall.bat short. Let us know if something doesn't succeed!
Go back to the SscBoogie\Binaries directory and type nmake register at the command prompt (this copies the binaries for the verifier back to where Spec# can find them).

Install and Build for Visual Studio 2008

If you have the option, we strongly recommend using Visual Studio 2010, since this is the version Spec# is currently developed and tested with. However, if you need to compile with 2008, you can follow exactly the same instructions above, after making the following change. For each of the following three files, find the two occurrences of ";DEV10" (which should be within "DefineConstants" tags), and delete them (just the DEV10 - leave the other constants there): SpecSharp/Microsoft.VisualStudio.CodeTools/PropertyPage/PropertyPage.csproj SpecSharp/Microsoft.VisualStudio.CodeTools/TaskManager/TaskManager.csproj SpecSharp/Microsoft.VisualStudio.Package/Microsoft.VisualStudio.Package.csproj

Updated Wiki: Sources

wuestholz — Mon, 25 Jul 2011 19:25:16 GMT

How to install and build the sources

Install and Build for Visual Studio 2010 (for 2008, see remarks below)

Some users have reported problems when working under cygwin due to unexpected access permissions and file ownership; we strongly recommend using the Visual Studio 2010 Command Prompt.

Spec#

Navigate to the SpecSharp\Microsoft.SpecSharp\LastKnownGood10 directory. Execute "Clean.cmd" and "RegisterLKG.cmd". You will need to have Administrator privileges in order to execute these scripts, and you need regasm.exe on your path (you may need to right-click on the Visual Studio 2010 Command Prompt and select Run as Administrator). This registers the Spec# compiler that comes in the LastKnownGood10 directory with Visual Studio so that Spec# projects can be loaded into Visual Studio and built. Some of the projects in the compiler are Spec# projects: the compiler is partially boot-strapped. If you get errors saying that RegAsm could not load a dll, try unblocking that dll (right-click the file ==> Properties ==> Unblock).
Open up SpecSharp10.sln in Visual Studio 2010 and build the "Debug" configuration (which should be selected by default). Right click on the "Checkin Tests" project and build it to make sure the regressions pass (one of the regression tests fails if the language of your Windows installation is not English; just ignore that test case).
The previous step builds a new version of the Spec# binaries. If you want to register the new version with Visual Studio, then you should close the Visual Studio IDE, and (using a command prompt with administrator privileges) navigate to the SpecSharp\Microsoft.SpecSharp\Registration directory. Execute "RegisterCurrent.cmd" to register your new version with Visual Studio. If you want to deregister this version, execute the "Clean.cmd" script in this directory.
If your registered version of Spec# becomes unusable in VisualStudio for any reason, you can try deregistering and registering it again, by repeating (with Visual Studio closed) either step 1 (to go back to the bootstrap version) or step 3 (for your currently-compiled version) above.
Note that to run the Spec# verifier with a new version, you need to build SscBoogie, as described below.

SscBoogie (after successfully compiling Spec#)

Navigate to the SscBoogie\Binaries directory, and type nmake at a command prompt (this makes local copies of various needed Spec# binaries).
In the SscBoogie\Source directory, either open SscBoogie.sln in Visual Studio and build the Debug configuration, or from a command prompt type devenv SscBoogie.sln /build Debug.
In the SscBoogie\Test directory, execute runtestall.bat short. Let us know if something doesn't succeed!
Go back to the SscBoogie\Binaries directory and type nmake register at the command prompt (this copies the binaries for the verifier back to where Spec# can find them).

Install and Build for Visual Studio 2008

If you have the option, we strongly recommend using Visual Studio 2010, since this is the version Spec# is currently developed and tested with. However, if you need to compile with 2008, you can follow exactly the same instructions above, after making the following change. For each of the following three files, find the two occurrences of ";DEV10" (which should be within "DefineConstants" tags), and delete them (just the DEV10 - leave the other constants there): SpecSharp/Microsoft.VisualStudio.CodeTools/PropertyPage/PropertyPage.csproj SpecSharp/Microsoft.VisualStudio.CodeTools/TaskManager/TaskManager.csproj SpecSharp/Microsoft.VisualStudio.Package/Microsoft.VisualStudio.Package.csproj

Updated Wiki: Sources

wuestholz — Mon, 25 Jul 2011 19:23:23 GMT

How to install and build the sources

Install and Build for Visual Studio 2010 (for 2008, see remarks below)

Some users have reported problems when working under cygwin due to unexpected access permissions and file ownership; we strongly recommend using the Visual Studio 2010 Command Prompt.

Spec#

Navigate to the SpecSharp\Microsoft.SpecSharp\LastKnownGood10 directory. Execute "Clean.cmd" and "RegisterLKG.cmd". You will need to have Administrator privileges in order to execute these scripts, and you need regasm.exe on your path (you may need to right-click on the Visual Studio 2010 Command Prompt and select Run as Administrator). This registers the Spec# compiler that comes in the LastKnownGood10 directory with Visual Studio so that Spec# projects can be loaded into Visual Studio and built. Some of the projects in the compiler are Spec# projects: the compiler is partially boot-strapped. If you get errors saying that RegAsm could not load a dll, try unblocking that dll (right-click the file ==> Properties ==> Unblock).
Open up SpecSharp10.sln in Visual Studio 2010 and build the "Debug" configuration (which should be selected by default). Right click on the "Checkin Tests" project and build it to make sure the regressions pass (one of the regression tests fails if the language of your Windows installation is not English; just ignore that test case).
The previous step builds a new version of the Spec# binaries. If you want to register the new version with Visual Studio, then you should close the Visual Studio IDE, and (using a command prompt with administrator privileges) navigate to the SpecSharp\Microsoft.SpecSharp\Registration directory. Execute "RegisterCurrent.cmd" to register your new version with Visual Studio. If you want to deregister this version, execute the "Clean.cmd" script in this directory.
If your registered version of Spec# becomes unusable in VisualStudio for any reason, you can try deregistering and registering it again, by repeating (with Visual Studio closed) either step 1 (to go back to the bootstrap version) or step 3 (for your currently-compiled version) above.
Note that to run the Spec# verifier with a new version, you need to build SscBoogie, as described below.

SscBoogie (after successfully compiling Spec#)

Navigate to the SscBoogie\Binaries directory, and type nmake at a command prompt (this makes local copies of various needed Spec# binaries).
In the SscBoogie\Source directory, either open SscBoogie.sln in Visual Studio and build the Debug configuration, or from a command prompt type devenv SscBoogie.sln /build Debug.
In the SscBoogie\Test directory, execute runtestall.bat short. Let us know if something doesn't succeed!
Go back to the SscBoogie\Binaries directory and type nmake register at the command prompt (this copies the binaries for the verifier back to where Spec# can find them).

Install and Build for Visual Studio 2008

If you have the option, we strongly recommend using Visual Studio 2010, since this is the version Spec# is currently developed and tested with. However, if you need to compile with 2008, you can follow exactly the same instructions above, after making the following change. For each of the following three files, find the two occurrences of ";DEV10" (which should be within "DefineConstants" tags), and delete them (just the DEV10 - leave the other constants there): SpecSharp/Microsoft.VisualStudio.CodeTools/PropertyPage/PropertyPage.csproj SpecSharp/Microsoft.VisualStudio.CodeTools/TaskManager/TaskManager.csproj SpecSharp/Microsoft.VisualStudio.Package/Microsoft.VisualStudio.Package.csproj

New Comment on "Binaries"

akku — Sat, 02 Jul 2011 09:34:38 GMT

Hi! I am trying to run spec# on VS2010 Ultimate, I did run command prompt as admin, executed register.cmd But nothing seems to happen, I can not understand the concept, it is really smth complicated. Can you provide more comprehensive instructions on how to run spec# in MVS2010 Thank you!