boogie Wiki & Documentation Rss Feed

Updated Wiki: Home

rustanleino — Fri, 15 Feb 2013 22:15:46 GMT

Microsoft Research Boogie

Boogie is an Intermediate Verification Language (IVL) for describing proof obligations to be discharged by a reasoning engine, typically an SMT solver. The language is especially suitable when the proof obligations arise in the context of programs with control flow and imperative state. The intermediate language is easy to target from source languages such as C# or C. Boogie is also a verification engine that takes the Boogie language as input, generates verification conditions (VCs) for the proof obligations, and passes the VCs to a reasoning engine. In the Boogie pipeline, there is room for various Boogie-to-Boogie transforms that either encode certain features (like parallelism) or make the checking more effective or efficient.

Frequently asked questions
External Dependencies
How to install the binaries
How to install and build the sources
How to install and build the sources using Mono (for OS X and Linux platforms)
How to run the Boogie Verification Debugger
How to contribute
MSR Boogie site
BOOGIE 2011: first international workshop on intermediate verification languages*

This project is sponsored by the Research in Software Engineering Group (RiSE) based in the Microsoft Research Redmond Laboratory.

Now you can try Boogie from your webbrowser at the RiSE4Fun website. The website also supports Dafny.

New Comment on "SourcesMono"

colinadams — Sat, 09 Feb 2013 20:20:39 GMT

The link for the Z3 download: http://research.microsoft.com/en-us/um/redmond/projects/z3/download.html does not exisy

Updated Wiki: Home

pcc — Fri, 04 May 2012 00:34:22 GMT

Microsoft Research Boogie

(aka The World's Best Program Verification System)
Boogie is a program verification system that produces verification conditions for programs written in an intermediate language (also named Boogie). The intermediate language is easy to target from source languages such as Spec#, C#, or even C.

Frequently asked questions
External Dependencies
How to install the binaries
How to install and build the sources
How to install and build the sources using Mono (for OS X and Linux platforms)
How to run the Boogie Verification Debugger
How to contribute
MSR Boogie site
BOOGIE 2011: first international workshop on intermediate verification languages*

Updated Wiki: SourcesMono

pcc — Fri, 04 May 2012 00:33:21 GMT

How to install and build the sources using Mono

Boogie can be built and run on Mac OS X and Linux machines following the instructions below.

Prerequisites

Mono; http://www.mono-project.com/, apt-get install mono-devel, etc.
Z3; download the correct version for your platform here.

Building

Go to the Sources directory and use the xbuild command to build the Boogie.sln solution.

cd /path/to/boogie/Sources
xbuild Boogie.sln

Note that projects other than Boogie itself (i.e. Dafny, Chalice, BCT) have not yet been tested under Mono.

Running

Boogie will try to find Z3 in its Binaries directory, named z3.exe. You can make this available by creating a symlink as below:

ln -s /path/to/z3/bin/z3 /path/to/boogie/Binaries/z3.exe

Now you can run Boogie using mono:

mono /path/to/boogie/Binaries/Boogie.exe input.bpl

You may wish to create an alias for easy access in your .bashrc or similar:

alias boogie='mono /path/to/boogie/Binaries/Boogie.exe'

Updated Wiki: Binaries

rustanleino — Mon, 12 Mar 2012 23:39:23 GMT

Go to the "Download" tab (to the right, or use the Downloads tab above) and click on the current release to download a zip file containing all of the binaries you need to run Boogie (and Dafny). Please let us know if something doesn't work!

After you download the Boogie zip file, you'll need to tell Windows to unblock its contents. To do that, right-click on the zip file, select Properties, click the Unblock button, and click OK. You can then unzip the contents into the folder of your choice.

You need some underlying prover to run Boogie. We recommend Z3 (of which you'll need version 3.2 or later), see the Z3 page for download/installation information. Note, Boogie will find Z3 if you install it according to the default settings in the Z3 installer. However, if you have a copy of z3.exe in the Boogie binaries directory, Boogie will prefer that copy. You can use Boogie's /trace flag to see where Boogie is getting Z3 from, and there are also command-line flags for letting you specify a different location (see /help).

The Boogie zip file also contains Dafny. However, it does not include the Dafny mode for Visual Studio. To install the Dafny mode for Visual Studio, you need to build from sources.

Apparently some people persist in using a 1970s operating system. If you are one of those unfortunate people, then Zvonimir Rakamaric has written a tutorial on how to run Boogie under Linux.

NOTE: The new bytecode translator is not included in the binary release. It will be once it is fully functional.

Updated Wiki: Binaries

rustanleino — Tue, 08 Nov 2011 02:34:08 GMT

Go to the "Download" tab and click on the current release to download a zip file containing all of the binaries you need to just run Boogie. Please let us know if something doesn't work!

After you download the Boogie zip file, you'll need to tell Windows to unblock its contents. To do that, right-click on the zip file, select Properties, click the Unblock button, and click OK. You can then unzip the contents into the folder of your choice.

You need some underlying prover to run Boogie. We recommend Z3 (of which you'll need version 3.2 or later), see the Z3 page for download/installation information. Note, Boogie will find Z3 if you install it according to the default settings in the Z3 installer. However, if you have a copy of z3.exe in the Boogie binaries directory, Boogie will prefer that copy. You can use Boogie's /trace flag to see where Boogie is getting Z3 from, and there are also command-line flags for letting you specify a different location (see /help).

The Boogie zip file also contains Dafny. However, it does not include the Dafny mode for Visual Studio. To install the Dafny mode for Visual Studio, you need to build from sources.

Apparently some people persist in using a 1970s operating system. If you are one of those unfortunate people, then Zvonimir Rakamaric has written a tutorial on how to run Boogie under Linux.

NOTE: The new bytecode translator is not included in the binary release. It will be once it is fully functional.

Updated Wiki: Sources

wuestholz — Wed, 26 Oct 2011 12:55:27 GMT

How to install and build the sources

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 2008 Command Prompt.
The build process seems to work more smoothly if you start the build steps from the command line rather than Visual Studio.

Boogie

To build Boogie: start by navigating to the Boogie/Source directory. Then either open Boogie.sln in Visual Studio and build the Debug configuration, or else from a command prompt type devenv Boogie.sln /build Debug. After building it, at a command prompt in the Test diretory, execute runtestall.bat short. Note that some tests require Dafny (see below). If you have not built Dafny yet, ignore the error messages for those tests. Let us know if something doesn't succeed!
(Optional Step) If you want to change the parser, then you need to modify the grammar file (Source/Core/BoogiePL.atg) and run Coco/R. In order to do that, you will first need to get the "frame files" which Coco uses as input. Those are located on the Boogie Partners site.

Dafny

First, build Boogie. Then, in the Source directory, either open Dafny.sln in Visual Studio and build it, or else from a command prompt type devenv Dafny.sln /build Debug.

Chalice

Detailed instructions on how to build, run and test Chalice can be found in the file readme.txt, which resides in the Chalice directory.

BCT (Bytecode Translator)

Currently, this can be installed and built completely separately from the rest of Boogie. If you do not have the rest of the Boogie sources installed, then install the Boogie binaries from the Downloads tab and copy them into the BCT/Imported/Boogie directory. If you have installed the Boogie sources and built them, you can either copy them from the Binaries directory there, or else change the references from the BytecodeTranslator project to point to the Boogie/Binaries directory.
Install the sources for the CCI Code and Ast Components project. The recommended structure is to put the project in a directory CCICodePlex/Ast.
The project references to the CCI projects assume that the CCICodePlex directory is a sibling to the parent of the BCT directory. If this is not the case, then the project references to the CCI projects will appear unavailable in Visual Studio. You can remove them from the solution and add the following existing projects from wherever you installed the CCI sources. (You will also have to re-add them as external references to the BytecodeTranslator project.)
1. CCIROOT/Ast/Sources/CodeModel/CodeModel.csproj
2. CCIROOT/Ast/Sources/ILToCodeModel/ILToCodeModel.csproj
3. CCIROOT/Ast/Metadata/Sources/MetadataHelper/MetadataHelper.csproj
4. CCIROOT/Ast/Metadata/Sources/MetadataModel/MetadataModel.csproj
5. CCIROOT/Ast/Sources/MutableCodeModel/MutableCodeModel.csproj
6. CCIROOT/Ast/Metadata/Sources/MutableMetadataModel/MutableMetadataModel.csproj
7. CCIROOT/Ast/Metadata/Sources/PdbReader/PdbReader.csproj
8. CCIROOT/Ast/Metadata/Sources/PeReader/PeReader.csproj
9. CCIROOT/Ast/Metadata/Sources/SourceModel/SourceModel.csproj
Build the Debug configuration. If it doesn’t succeed, let us know!

Visual Studio integration

You can edit Dafny and Chalice programs inside Microsoft Visual Studio 2010. This gives you syntax highlighting and runs the verifier in the background, producing red squigglies for errors. To install this mode, you need to build it, which is done in Visual Studio 2010.

Install the Visual Studio 2010 SDK (or the Visual Studio 2010 SP1 SDK if you use Visual Studio 2010 SP1).
Open Util/VS2010/Dafny/DafnyLanguageService.sln (or the analogous .sln file for Chalice in a parallel directory) in Visual Studio 2010.
Build the project, which should report "Succeeded". Quit Visual Studio. Now, the Dafny (or Chalice) mode is available in the experimental instance of Visual Studio 2010. This experimental instance is part of the VS 2010 SDK you just installed.
The integration calls out to Dafny (or Chalice) in a primitive fashion, namely by invoking c:\tmp\StartDafny.bat. This path is currently hard coded, so create a directory c:\tmp and copy into it the file Util/VS2010/Dafny/StartDafny.bat.
Finally, open the experimental instance of Visual Studio 2010 and open any file with the .dfy (or .chalice) extension. You start it from Start -> All programs -> Microsoft Visual Studio 2010 SDK -> Tools. (You may want to right-click on it and select Pin To Start Menu for easy access.)

There is currently no project support for Dafny and Chalice programs, so if you want to add extra command-line options to the verifier, you have to do that by changing the batch file. Another limitation is that you have to create new .dfy files outside Visual Studio (you can then open them and edit them and save them inside Visual Studio, but you can't do the initial creation from inside Visual Studio, because then Visual Studio wants to append .txt to the end of the filename you're trying to create).

Updated Wiki: Sources

stefanheule — Wed, 03 Aug 2011 11:43:28 GMT

How to install and build the sources

Some users have reported problems when working under cygwin due to unexpected access permissions and file ownership; we strongly recommend using the Visual Studio 2008 Command Prompt.
The build process seems to work more smoothly if you start the build steps from the command line rather than Visual Studio.

Boogie

To build Boogie: start by navigating to the Boogie/Source directory. Then either open Boogie.sln in Visual Studio and build the Debug configuration, or else from a command prompt type devenv Boogie.sln /build Debug. After building it, at a command prompt in the Test diretory, execute runtestall.bat short. Note that some tests require Dafny (see below). If you have not built Dafny yet, ignore the error messages for those tests. Let us know if something doesn't succeed!
(Optional Step) If you want to change the parser, then you need to modify the grammar file (Source/Core/BoogiePL.atg) and run Coco/R. In order to do that, you will first need to get the "frame files" which Coco uses as input. Those are located on the Boogie Partners site.

Dafny

First, build Boogie. Then, in the Source directory, either open Dafny.sln in Visual Studio and build it, or else from a command prompt type devenv Dafny.sln /build Debug.

Chalice

Detailed instructions on how to build, run and test Chalice can be found in the file readme.txt, which resides in the Chalice directory.

BCT (Bytecode Translator)

Currently, this can be installed and built completely separately from the rest of Boogie. If you do not have the rest of the Boogie sources installed, then install the Boogie binaries from the Downloads tab and copy them into the BCT/Imported/Boogie directory. If you have installed the Boogie sources and built them, you can either copy them from the Binaries directory there, or else change the references from the BytecodeTranslator project to point to the Boogie/Binaries directory.
Install the sources for the CCI Code and Ast Components project. The recommended structure is to put the project in a directory CCICodePlex/Ast.
The project references to the CCI projects assume that the CCICodePlex directory is a sibling to the parent of the BCT directory. If this is not the case, then the project references to the CCI projects will appear unavailable in Visual Studio. You can remove them from the solution and add the following existing projects from wherever you installed the CCI sources. (You will also have to re-add them as external references to the BytecodeTranslator project.)
1. CCIROOT/Ast/Sources/CodeModel/CodeModel.csproj
2. CCIROOT/Ast/Sources/ILToCodeModel/ILToCodeModel.csproj
3. CCIROOT/Ast/Metadata/Sources/MetadataHelper/MetadataHelper.csproj
4. CCIROOT/Ast/Metadata/Sources/MetadataModel/MetadataModel.csproj
5. CCIROOT/Ast/Sources/MutableCodeModel/MutableCodeModel.csproj
6. CCIROOT/Ast/Metadata/Sources/MutableMetadataModel/MutableMetadataModel.csproj
7. CCIROOT/Ast/Metadata/Sources/PdbReader/PdbReader.csproj
8. CCIROOT/Ast/Metadata/Sources/PeReader/PeReader.csproj
9. CCIROOT/Ast/Metadata/Sources/SourceModel/SourceModel.csproj
Build the Debug configuration. If it doesn’t succeed, let us know!

Visual Studio integration

Install the Visual Studio 2010 SDK.
Open Util/VS2010/Dafny/DafnyLanguageService.sln (or the analogous .sln file for Chalice in a parallel directory) in Visual Studio 2010.
Build the project, which should report "Succeeded". Quit Visual Studio. Now, the Dafny (or Chalice) mode is available in the experimental instance of Visual Studio 2010. This experimental instance is part of the VS 2010 SDK you just installed.
The integration calls out to Dafny (or Chalice) in a primitive fashion, namely by invoking c:\tmp\StartDafny.bat. This path is currently hard coded, so create a directory c:\tmp and copy into it the file Util/VS2010/Dafny/StartDafny.bat.
Finally, open the experimental instance of Visual Studio 2010 and open any file with the .dfy (or .chalice) extension. You start it from Start -> All programs -> Microsoft Visual Studio 2010 SDK -> Tools. (You may want to right-click on it and select Pin To Start Menu for easy access.)

Updated Wiki: Home

rustanleino — Wed, 03 Aug 2011 07:17:26 GMT

Microsoft Research Boogie

Frequently asked questions
External Dependencies
How to install the binaries
How to install and build the sources
How to run the Boogie Verification Debugger
How to contribute
MSR Boogie site
BOOGIE 2011: first international workshop on intermediate verification languages*

Updated Wiki: Documentation

rustanleino — Thu, 28 Jul 2011 21:28:04 GMT

Documentation

Boogie

Dafny

Chalice

BCT The BCT is the byte-code translator that takes MSIL from a .NET compiler and produces a Boogie program. It is built on top of CCI. It is (woefully) incomplete, but under active development. Please get in touch if you would like to help with the effort!

Updated Wiki: Home

rustanleino — Thu, 28 Jul 2011 21:22:10 GMT

Microsoft Research Boogie

Updated Wiki: Binaries

mikebarnett — Tue, 03 May 2011 22:53:51 GMT

Go to the "Download" tab and click on the current release to download a zip file containing all of the binaries you need to just run Boogie. Please let us know if something doesn't work!

Apparently some people persist in using a 1970s operating system. If you are one of those unfortunate people, then Zvonimir Rakamaric has written a tutorial on how to run Boogie under Linux.

NOTE: The new bytecode translator is not included in the binary release. It will be once it is fully functional.

Updated Wiki: BVD

rustanleino — Thu, 10 Mar 2011 01:39:58 GMT

The Boogie Verification Debugger (BVD) is a tool with an interface akin to that of dynamic debuggers. It lets users learn more about failed verifications by inspecting the values of variables in the counterexample provided by the theorem prover. BVD currently has plug-ins for VCC and for Dafny, and it works with Z3 as the theorem prover.

Using BVD with VCC

You need to use VCC3, i.e., the new VCC memory model. Run VCC as follows:

  vcc -3 -cev:foo.model foo.c

This will create file "foo.model", then run:

  bvd foo.model

Using BVD with Dafny

Run:

  dafny -mv:foo.model foo.dfy

This will create file "foo.model", then run:

  bvd foo.model

Using BVD with Boogie

Run:

  boogie -mv:foo.model foo.bpl

This will create file "foo.model", then run:

  bvd foo.model

Note that the model is displayed with no interpretation, and thus might be huge and confusing.

Updated Wiki: Home

rustanleino — Thu, 10 Mar 2011 01:31:16 GMT

Microsoft Research Boogie

Updated Wiki: Home

MichalMoskal — Tue, 01 Feb 2011 22:55:23 GMT

Microsoft Research Boogie

Updated Wiki: External Dependencies

mikebarnett — Wed, 08 Dec 2010 20:49:39 GMT

External Dependencies

Things you must have in order to build Boogie

.NET 4.0: Boogie is a .NET application, so you must have the framework installed.

Things you might need in order to build Boogie

Coco/R: Boogie's parser uses Coco/R. You do not need to install Coco/R unless you plan on changing the Boogie language or the scanner/parser itself.
CCI: You will need to install the sources for CCI if you want to build the BCT (Bytecode Translator) project. Currently, the BCT is not used by Boogie, so you shouldn't need this project unless you are involved with its development.

Things you need in order to run Boogie

Z3: Boogie's default is to generate verification conditions for Z3. Other theorem provers can also be used, e.g., Simplify. You need some theorem prover if you wish to actually find out whether a Boogie program is correct or not.

Updated Wiki: Binaries

mikebarnett — Tue, 07 Dec 2010 18:27:28 GMT

Go to the "Download" tab and click on the current release to download a zip file containing all of the binaries you need to just run Boogie. Please let us know if something doesn't work!

Apparently some people persist in using a 1970s operating system. If you are one of those unfortunate people, then Zvonomir Rakamaric has written a tutorial on how to run Boogie under Linux.

NOTE: The new bytecode translator is not included in the binary release. It will be once it is fully functional.

Updated Wiki: External Dependencies

mikebarnett — Mon, 06 Dec 2010 23:00:35 GMT

External Dependencies

Things you must have in order to build Boogie

.NET 4.0: Boogie is a .NET application, so you must have the framework installed.

Things you might need in order to build Boogie

Coco/R: Boogie's parser uses Coco/R. You do not need to install Coco/R unless you plan on changing the Boogie language or the scanner/parser itself.
CCI: You will need to install the sources for CCI if you want to build the BCT (Bytecode Translator) project. Currently, the BCT is not used by Boogie, so you shouldn't need this project unless you are involved with its development.

Things you need in order to run Boogie

Z3: Boogie's default is to generate verification conditions for Z3. Other theorem provers can also be used, e.g., Simplify. You need some theorem prover if you wish to actually find out whether a Boogie program is correct or not.

Updated Wiki: Sources

mikebarnett — Wed, 01 Dec 2010 17:53:21 GMT

How to install and build the sources

Some users have reported problems when working under cygwin due to unexpected access permissions and file ownership; we strongly recommend using the Visual Studio 2008 Command Prompt.
The build process seems to work more smoothly if you start the build steps from the command line rather than Visual Studio.

Boogie

To build Boogie: start by navigating to the Boogie/Source directory. Then either open Boogie.sln in Visual Studio and build the Debug configuration, or else from a command prompt type devenv Boogie.sln /build Debug. After building it, at a command prompt in the Test diretory, execute runtestall.bat short. Note that some tests require Dafny (see below). If you have not built Dafny yet, ignore the error messages for those tests. Let us know if something doesn't succeed!
(Optional Step) If you want to change the parser, then you need to modify the grammar file (Source/Core/BoogiePL.atg) and run Coco/R. In order to do that, you will first need to get the "frame files" which Coco uses as input. Those are located on the Boogie Partners site.

Dafny

First, build Boogie. Then, in the Source directory, either open Dafny.sln in Visual Studio and build it, or else from a command prompt type devenv Dafny.sln /build Debug.

Chalice

To build Chalice, you need to have installed Scala and a JVM. In the Chalice directory, run nmake from a command prompt. To run the Chalice test suite, run test.bat in the Chalice directory. You might have to increase the stack size of the JVM to avoid a stack overflow, for instance by changing scala.bat by adding "-Xss16M" to the JAVA_OPTS:
if "%_JAVA_OPTS%"=="" set _JAVA_OPTS=-Xmx256M -Xms32M -Xss16M

BCT (Bytecode Translator)

Currently, this can be installed and built completely separately from the rest of Boogie. If you do not have the rest of the Boogie sources installed, then install the Boogie binaries from the Downloads tab and copy them into the BCT/Imported/Boogie directory. If you have installed the Boogie sources and built them, you can either copy them from the Binaries directory there, or else change the references from the BytecodeTranslator project to point to the Boogie/Binaries directory.
Install the sources for the CCI Code and Ast Components project. The recommended structure is to put the project in a directory CCICodePlex/Ast.
The project references to the CCI projects assume that the CCICodePlex directory is a sibling to the parent of the BCT directory. If this is not the case, then the project references to the CCI projects will appear unavailable in Visual Studio. You can remove them from the solution and add the following existing projects from wherever you installed the CCI sources. (You will also have to re-add them as external references to the BytecodeTranslator project.)
1. CCIROOT/Ast/Sources/CodeModel/CodeModel.csproj
2. CCIROOT/Ast/Sources/ILToCodeModel/ILToCodeModel.csproj
3. CCIROOT/Ast/Metadata/Sources/MetadataHelper/MetadataHelper.csproj
4. CCIROOT/Ast/Metadata/Sources/MetadataModel/MetadataModel.csproj
5. CCIROOT/Ast/Sources/MutableCodeModel/MutableCodeModel.csproj
6. CCIROOT/Ast/Metadata/Sources/MutableMetadataModel/MutableMetadataModel.csproj
7. CCIROOT/Ast/Metadata/Sources/PdbReader/PdbReader.csproj
8. CCIROOT/Ast/Metadata/Sources/PeReader/PeReader.csproj
9. CCIROOT/Ast/Metadata/Sources/SourceModel/SourceModel.csproj
Build the Debug configuration. If it doesn’t succeed, let us know!

Visual Studio integration

Install the Visual Studio 2010 SDK.
Open Util/VS2010/Dafny/DafnyLanguageService.sln (or the analogous .sln file for Chalice in a parallel directory) in Visual Studio 2010.
Build the project, which should report "Succeeded". Quit Visual Studio. Now, the Dafny (or Chalice) mode is available in the experimental instance of Visual Studio 2010. This experimental instance is part of the VS 2010 SDK you just installed.
The integration calls out to Dafny (or Chalice) in a primitive fashion, namely by invoking c:\tmp\StartDafny.bat. This path is currently hard coded, so create a directory c:\tmp and copy into it the file Util/VS2010/Dafny/StartDafny.bat.
Finally, open the experimental instance of Visual Studio 2010 and open any file with the .dfy (or .chalice) extension. You start it from Start -> All programs -> Microsoft Visual Studio 2010 SDK -> Tools. (You may want to right-click on it and select Pin To Start Menu for easy access.)

Updated Wiki: Sources

mikebarnett — Tue, 09 Nov 2010 19:45:51 GMT

How to install and build the sources

Some users have reported problems when working under cygwin due to unexpected access permissions and file ownership; we strongly recommend using the Visual Studio 2008 Command Prompt.
The build process seems to work more smoothly if you start the build steps from the command line rather than Visual Studio.

Boogie

Although Boogie is written in C# and so is compiled by the C# compiler, it retains (for now) a binary dependence on the Spec# binaries. These binaries are the ones checked into the Boogie/Binaries directory, so you should not have to do anything. We hope to remove these dependencies in the near future. This item is just to make you aware of the situation in case you run into any problems while building Boogie.
To build Boogie: start by navigating to the Boogie/Source directory. Then either open Boogie.sln in Visual Studio and build the Debug configuration, or else from a command prompt type devenv Boogie.sln /build Debug. After building it, at a command prompt in the Test diretory, execute runtestall.bat short. Note that some tests require Dafny (see below). If you have not built Dafny yet, ignore the error messages for those tests. Let us know if something doesn't succeed!
(Optional Step) If you want to change the parser, then you need to modify the grammar file (Source/Core/BoogiePL.atg) and run Coco/R. In order to do that, you will first need to get the "frame files" which Coco uses as input. Those are located on the Boogie Partners site.

Dafny

First, build Boogie. Then, in the Source directory, either open Dafny.sln in Visual Studio and build it, or else from a command prompt type devenv Dafny.sln /build Debug.

Chalice

BCT (Bytecode Translator)

Currently, this can be installed and built completely separately from the rest of Boogie. If you do not have the rest of the Boogie sources installed, then install the Boogie binaries from the Downloads tab and copy them into the BCT/Imported/Boogie directory. If you have installed the Boogie sources and built them, you can either copy them from the Binaries directory there, or else change the references from the BytecodeTranslator project to point to the Boogie/Binaries directory.
Install the sources for the CCI Code and Ast Components project. The recommended structure is to put the project in a directory CCICodePlex/Ast.
The project references to the CCI projects assume that the CCICodePlex directory is a sibling to the parent of the BCT directory. If this is not the case, then the project references to the CCI projects will appear unavailable in Visual Studio. You can remove them from the solution and add the following existing projects from wherever you installed the CCI sources. (You will also have to re-add them as external references to the BytecodeTranslator project.)
1. CCIROOT/Ast/Sources/CodeModel/CodeModel.csproj
2. CCIROOT/Ast/Sources/ILToCodeModel/ILToCodeModel.csproj
3. CCIROOT/Ast/Metadata/Sources/MetadataHelper/MetadataHelper.csproj
4. CCIROOT/Ast/Metadata/Sources/MetadataModel/MetadataModel.csproj
5. CCIROOT/Ast/Sources/MutableCodeModel/MutableCodeModel.csproj
6. CCIROOT/Ast/Metadata/Sources/MutableMetadataModel/MutableMetadataModel.csproj
7. CCIROOT/Ast/Metadata/Sources/PdbReader/PdbReader.csproj
8. CCIROOT/Ast/Metadata/Sources/PeReader/PeReader.csproj
9. CCIROOT/Ast/Metadata/Sources/SourceModel/SourceModel.csproj
Build the Debug configuration. If it doesn’t succeed, let us know!

Visual Studio integration

Install the Visual Studio 2010 SDK.
Open Util/VS2010/Dafny/DafnyLanguageService.sln (or the analogous .sln file for Chalice in a parallel directory) in Visual Studio 2010.
Build the project, which should report "Succeeded". Quit Visual Studio. Now, the Dafny (or Chalice) mode is available in the experimental instance of Visual Studio 2010. This experimental instance is part of the VS 2010 SDK you just installed.
The integration calls out to Dafny (or Chalice) in a primitive fashion, namely by invoking c:\tmp\StartDafny.bat. This path is currently hard coded, so create a directory c:\tmp and copy into it the file Util/VS2010/Dafny/StartDafny.bat.
Finally, open the experimental instance of Visual Studio 2010 and open any file with the .dfy (or .chalice) extension. You start it from Start -> All programs -> Microsoft Visual Studio 2010 SDK -> Tools. (You may want to right-click on it and select Pin To Start Menu for easy access.)