recentquestions | Channel 9

Summary: This page contains links to recently asked questions.

Back to the HomePage.

If a Wiki word sounds like what you are asking, please check that link out first.

If you are looking into uncharted territory, simply add your question(s) and hope for a helpful response. After a reasonable period of time for comment and review, a question raised here may be moved to the FrequentlyAskedQuestions page. More obscure questions may eventually be removed or moved to the AncientQuestions page.

Purely Spec#

This section is for questions dealing with Spec# the language.

Development Environment

This section is for questions involving usage of the Spec# development environment, whether IDE or command line.

Visual Studio 2005 (or 2003) interaction

Project stored on removable media: I had been experimenting with placing my projects on solid-state removable media to see if there would be a performance improvement. Unfortunately they never compiled correctly, with symptoms reminiscient of the FooNotFoo problem. The exact same workspace compiled fine on non-removable media. I suspect this more a .NET assembly problem than Spec# related, but was wondering if anyone has encountered something similar. -- BrianStrelioff
Project References: I am attempting to Test my Spec# Class Library Project (""SpecSample"") by creating another C# Class Library Project in the Solution and Referencing the Spec# Project. While Add Reference/Projects does find the Spec# project, I can not seem to use the Namespaces in the Spec# project. The Reference Properties indicate that I am referencing the bin/debug/SpecSample.dll. The Spec# Namespace is not appearing in the Class View either. What must I do to reference my Spec# project in another Project in VS2005? -- MattScilipoti

Request: Preview does not show a border for this table. If someone could add the formatting (then delete this request), I'd appreciate it.

ITEM	VERSION	NOTES
Microsoft Visual Studio 2005	Version 8.0.50727.51 (QFE.050727-5100)
Microsoft .NET Framework	Version 2.0.50727
Microsoft Visual C# 2005	77626-009-0932016-41892
Hotfix for Microsoft Visual Studio 2005 Professional Edition	ENU (KB910275)	This Hotfix is for Microsoft Visual Studio 2005 Professional Edition - ENU.
Microsoft.SpecSharp	1.0.6404.0
Microsoft® Spec# Compiler	Version 1.0.6404.0
ReSharper 2.0	(build #263)	ReSharper add-in for Microsoft Visual Studio. For more information about ReSharper, see the ReSharper website at http://www.jetbrains.com/resharper. Copyright (c) 2003-2006 JetBrains, Inc
TestDriven.NET	2.0.1544.0	For more information, see the TestDriven.NET website at http://www.testdriven.net/. Development by Jamie Cansdale <jamie@mutantdesign.co.uk>. Copyright (c) 2004 Mutant Design.

Empty Solutions I've just installed Spec# on Vista (build 5744) with VS 2005 (8.0.50727.42). I can build just fine from the command line, but when I attempt to create a project within VS, the solution pane is empty. The appropriate files are created on the disk (i.e., Program.ssc, AssemblyInfo.ssc & Project1.sscproj), and the Program.ssc file opens in the VS editor. It even builds! But since there's nothing in the solution pane, there's no way to look at the project properties, no way to add new files etc. Anyone got any ideas? -- srstrong
Empty Solutions - Update Just tried a Spec# install on an XP box, and it's working just fine, so I'm guessing that something is amiss with the installation on Vista. -- srstrong

Spec# Wiki Usage

User Identification: I am accessing this Wiki uwing my Microsoft Passport information, and somehow was assigned the moniker 000147D0425B883B, which is a bit of a tongue-twister. Does anybudy know how this happened (i.e. is it a anonymity feature), and how I can change it to a more friendly id? -- BrianStrelioff

		         *A:* It seems that you can avoid this glitch by logging in directly using a Channel9 account rather than through .NET Passport. It seems to work for me. -- Bart Jacobs

Visual Studio 2005 (and 2008) MSBuild Tasks for Spec#

What needs to be done to for a C# project in Visual Studio to recognise Spec# code?
Is is possible to add an MSBuild Task to compile such code from within a C# project?