Jeremy Kuhne's Blog : SSCLI

Creating a SSCLI C# Template for Visual Studio

jkuhne — Sat, 23 Feb 2008 08:29:00 GMT

In my last post (MSBuild your SSCLI C# projects) I demonstrated how to create an MSBuild targets file for the SSCLI (Rotor). In this post I'll show you how to make it easier to use Visual Studio to develop SSCLI C# projects.

To build successfully in VS you need to do a few things, notably:

Override assembly resolution so the SSCLI assemblies are targeted (the last post shows you how to do this)
Change the startup action for the project to "Start external program" (in the Debug property page for the project)
Enter the path for clix.exe as the startup program
Put the output binary for you application in as the "Command line arguments"

It's a little tedious to set all of this up by hand. Thankfully it ends up it's pretty easy to make a template to do most of the dirty work. With a small additional change to the targets file it makes it completely painless. (Well, with the one major caveat that you can't debug managed SSCLI code with VS.)

The existing templates are in the VS folder under "Common7\IDE\ProjectTemplates". Each of the templates are stored in a zip file- perusing a few of these in addition to looking at the documentation will get you up to speed in no time. As such I'm not going to give a tutorial here, I'm just going to talk briefly about what I did to create my template and share it with you.

I started with the "CSharp\Windows\1033\ConsoleApplication.zip" because I wanted the equivalent of that for SSCLI. I had to make most of the changes to the .vstemplate file and a few changes to the .csproj file to link in my targets. Here is what my .vstemplate file looks like:

<?xml version="1.0" encoding="utf-8"?>

<Name>SSCLI Console Application</Name>

<Description>Console Application for the SSCLI (Rotor) Framework</Description>

<Icon>SSCLIConsole.ico</Icon>

<TemplateID>SSCLI.CSharp.ConsoleApplication</TemplateID>

<ProjectType>CSharp</ProjectType>

<DefaultName>SSCLIConsoleApplication</DefaultName>

</TemplateData>

<ProjectItem ReplaceParameters="true" TargetFileName="Properties\AssemblyInfo.cs">AssemblyInfo.cs</ProjectItem>

<ProjectItem ReplaceParameters="true" OpenInEditor="true">Program.cs</ProjectItem>

</Project>

</TemplateContent>

</VSTemplate>

Not too hard to wrap your head around. In the .csproj I changed the import to

<Import Project="$(MSBuildToolsPath)\SSCLI.CSharp.targets" />

Zipped up with a custom icon (had to try it) I dumped it in my "Documents\Visual Studio 2008\Templates\ProjectTemplates\Visual C#" folder, created a few projects off the template to tweak it out and I was almost done.

The other bit that I've already mentioned was setting the project properties to run "clix". Figuring this bit out isn't too terribly straightforward. VS project settings that don't go into the .csproj go into a ".csproj.user" file that is created alongside your .csproj whenever you change the defaults. Change the defaults to create said file and you'll quickly discover what you need to set in your .targets file to establish your own defaults. (Note that these properties are listed in the Microsoft.Build.Commontypes.xsd, found in the MSBuild directory in your relevant framework directory. Also note that it doesn't contain valid values for the VS properties.)

Here is what I added to SSCLI.CSharp.targets (which should live in your MSBuild directory):

<StartAction>Program</StartAction>

<StartProgram>$(SSCLI_FrameworkPath)\clix.exe</StartProgram>

<StartArguments>$(TargetFileName)</StartArguments>

</PropertyGroup>

That's pretty much it. Now you can relatively easily create SSCLI projects. You don't get managed debugging, as mentioned. You do get the rest of the development enviroment benefits however (intellisense, etc.).

The complete SSCLI.CSharp.targets file can be found here. The template can be found here.

MSBuild your SSCLI C# projects

jkuhne — Wed, 20 Feb 2008 09:21:00 GMT

[ Edit 22 Feb 2008: The complete SSCLI.CSharp.targets file can be found here. ]

In my last post I got SSCLI compiling with the 2008 C++ compiler (SSCLI 2.0 and Visual Studio 2008). (A side note: since it is clearly possible to build SSCLI with the compiler there is no reason you shouldn't be able to get a VS Solution up and running that would build the SSCLI- just a lot of work.) Having done that I thought it would be interesting to see how plausible actually working in VS with SSCLI projects would be.

As a first step, it ends up that there is relatively little you have to do to get a .csproj that will work with SSCLI through MSBuild. The key items are:

Set the Csc.exe path.
Make sure the TargetFrameworkDirectory gets set to the SSCLI output directory.

The way to figure this out is to work backwards from the compiler (csc.exe). Look at what csc's arguments are and look for where arguments get generated for it in the build targets.

Microsoft.CSharp.targets is the file to start looking in. It is included at the end of a .csproj so this is a pretty logical place to start looking. Thankfully the file is short, so it is relatively easy to digest. (The target files are in the Windows\Microsoft.Net\Framework\v0.0 directories. I used 3.5 for this article- the last set of MSBuild targets before this version are in 2.0.50727.)

The <Csc> task in Microsoft.CSharp.Targets has a "ToolPath" argument that takes $(CscToolPath). There is #1! Finding #2 begins with "References" which is set to @(ReferencePath). You won't find much in Microsoft.CSharp.Targets so you need to look to the included Microsoft.Common.Targets.

You can figure out #2 by looking at the generation of @(ReferencePaths). Doing a search will drop you in the ResolveAssemblyReferences target- it's in the comments as an [OUT] -- bingo. In a csproj referenced .NET assemblies are listed under (logically) <Reference> items. These are listed here as an [IN] in the comments - see the connection? (Note: the quick way to look for usage of items is to search for '@(ItemName' -- don't use the closing parenthesis as you'll miss transforms.)

In this target the simple "System" <Reference> is turned into a full @(ReferencePaths) item. If you look at the <ResolveAssemblyReference> task within this target you'll see some promising parameters-- the most promising being SearchPaths="$(AssemblySearchPaths)". Look for the source of $(AsemblySearchPaths) and you'll find a nice detailed comment at the top of Common.Targets:

<!--

The SearchPaths property is set to find assemblies in the following order:

(1) Files from current project - indicated by {CandidateAssemblyFiles}

(2) $(ReferencePath) - the reference path property, which comes from the .USER file.

(3) The hintpath from the referenced item itself, indicated by {HintPathFromItem}.

(4) The directory of MSBuild's "target" runtime from GetFrameworkPath.

The "target" runtime folder is the folder of the runtime that MSBuild is a part of.

(5) Registered assembly folders, indicated by {Registry:*,*,*}

(6) Legacy registered assembly folders, indicated by {AssemblyFolders}

(7) Look in the application's output folder (like bin\debug)

(8) Resolve to the GAC.

(9) Treat the reference's Include as if it were a real file name.

-->

{CandidateAssemblyFiles};

$(ReferencePath);

{HintPathFromItem};

{TargetFrameworkDirectory};

{Registry:$(FrameworkRegistryBase),$(TargetFrameworkVersion),$(AssemblyFoldersSuffix)$(AssemblyFoldersExConditions)};

{AssemblyFolders};

{GAC};

{RawFileName};

$(OutDir)

</AssemblySearchPaths>

{TargetFrameworkDirectory} is key here. If you search for "TargetFrameworkDirectory" you'll find the property shows up in the GetFrameworkPaths and GetReferenceAssemblyPaths targets. It is the one we want. It gets replaced by $(TargetFrameworkDirectory) inside of the <ResolveAssemblyReference> task. You can see this if you use Reflector to look at the task-- but you can probably make that leap without digging further.

That gives us everything we need. We know where all of our framework (SSCLI) assemblies are so we just need to override Common.targets' path building completely for this and inject our overrides into the regular targets. You can do this by creating a new target file that includes the Microsoft.CSharp.targets and use this new file instead in your .csproj. Here's the answer:

<SSCLI_FrameworkPath>$(ROTOR_DIR)\binaries.x86chk.rotor</SSCLI_FrameworkPath>

<CscToolPath>$(SSCLI_FrameworkPath)</CscToolPath>

<TargetFrameworkDirectory>$(SSCLI_FrameworkPath)</TargetFrameworkDirectory>

</PropertyGroup>

<Target

Name="SSCLI_InitialChecks">

<Error

Condition=" '$(ROTOR_DIR)' == '' "

Text="ROTOR_DIR is not set. Please set an environment variable or property to the SSCLI directory. Note that running 'env' in your SSCLI directory will set this."/>

<Error

Condition="!Exists('$(SSCLI_FrameworkPath)')"

Text="SSCLI not found at expected path: '$(SSCLI_FrameworkPath)' Please build SSCLI if necessary." />

</Target>

<!--

Override Microsoft.Common.targets GetFrameworkPaths

-->

<Target

Name="GetFrameworkPaths"

DependsOnTargets="$(GetFrameworkPathsDependsOn)" />

<!--

Override Microsoft.Common.targets GetFrameworkPaths

-->

<Target

Name="GetReferenceAssemblyPaths"

DependsOnTargets="$(GetReferenceAssemblyPathsDependsOn)" />

</Project>

Dump the xml above into a file (say, called "SSCLI.CSharp.targets"), drop it in the same directory as the other target files, and (as already stated) include this file in your csproj instead of Microsoft.CSharp.targets.

Now you can 'msbuild myNiftySscliApp.csproj'. And yes, you can even open said csproj in Visual Studio and do some developin'. (With the sad lack of managed debugging, but, hey-- you get Intellisense and all of the other goodies of the IDE.) In my next posts I'll show you how to grease the wheels as much as you can with the IDE, starting with how to build and run easily, then moving on to making an SSCLI project template.

SSCLI 2.0 and Visual Studio 2008

jkuhne — Tue, 19 Feb 2008 12:30:00 GMT

The currently available SSCLI 2.0 (Rotor) does not build successfully with Visual Studio 2008. I've managed to make it build and I thought I'd share my changes. Be very aware:

I haven't done anything resembling thorough testing on these changes
I made the changes so that it would build for me on my 32bit Vista machine
I avoided changing source files, and focused on build files
The warnings I disabled are pretty tame, see #3
I tried to keep the changes to a minimum
I know next to nothing about NMAKE
I have no idea about any MS plans regarding SSCLI and VS2008
This is does not constitute official support for building SSCLI in VS2008

\sscli20\mswin32.startup.pl

change the if block that begins at line 41:

if (my $msvcdir = Get("MSVCDir")) {

    # These are the INCLUDE paths used during the primary bootstrap.

    my $winsdkdir = Get("ROTOR_WINSDKDIR");

    Set("SDK_INC_PATH_BOOT", catdir ($winsdkdir, "include"));

    Set("CRT_INC_PATH_BOOT", catdir ($msvcdir, "Include"));

    Set("SDK_LIB_PATH", catdir ($winsdkdir, "lib"));

    Set("CRT_LIB_PATH", catdir ($msvcdir, "lib"));

    Set("VC_BIN_PATH", catdir ($msvcdir, "bin"));

}

\sscli20\win.env.bat

change %VS80COMNTOOLS% on line 37 to %VS90COMNTOOLS%
after line 42, insert the following:

REM Set the SDK path

if "%ROTOR_WINSDKDIR%"=="" set ROTOR_WINSDKDIR=%WindowsSdkDir%

if "%ROTOR_WINSDKDIR%"=="" set ROTOR_WINSDKDIR=%MSVCDIR%\PlatformSDK

call :ShortName "%ROTOR_WINSDKDIR%"

set ROTOR_WINSDKDIR=%RESULT%

\sscli20\clr\src\classlibnative\nls\wks\sources; \sscli20\clr\src\debug\daccess\wks\sources; \sscli20\clr\src\vm\dacwks\sources; \sscli\clr\src\classlibnative\float\wks\sources; \sscli\clr\src\dlls\mscordac\wks\sources; \sscli\clr\src\vm\wks1\sources; \sscli\clr\src\vm\wks2\sources; \sscli\clr\src\vm\wks3\sources; \sscli\clr\src\vm\wks4\sources

Kill line 16 (MSC_WARNING_LEVEL =-Wp64)

\sscli\clr\src\classlibnative\float\sources.inc

Kill line 21 (COMPILER_WARNINGS =/W4)

\sscli20\clr\src\toolbox\sos\strike\sources

Kill line 18 (MSC_WARNING_LEVEL =/W4)

\env\bin\devdiv.def

Change line 334 to SUBSYSTEM_WINVER = ,5.00
Change line 338 to SUBSYSTEM_CONVER = ,5.00

\pal\inc\vs9.h (NEW FILE)

// Patch up the conflicting defines to allow building with VS9

#undef MAKEWORD

#undef MAKELONG

#undef LOWORD

#undef HIWORD

#undef LOBYTE

#undef HIBYTE

#undef IPPROTO_IP

#undef IPPROTO_ICMP

#undef IPPROTO_IGMP

#undef IPPROTO_GGP

#undef IPPROTO_TCP

#undef IPPROTO_PUP

#undef IPPROTO_UDP

#undef IPPROTO_IDP

#undef IPPROTO_ND

#undef IPPROTO_RAW

#undef INADDR_ANY

#undef INADDR_BROADCAST

#undef INADDR_NONE

#pragma warning (disable :4985)

#define IMAGE_SIZEOF_NT_OPTIONAL32_HEADER    224

#define IMAGE_SIZEOF_NT_OPTIONAL64_HEADER    240

#ifdef _WIN64

#define IMAGE_SIZEOF_NT_OPTIONAL_HEADER     IMAGE_SIZEOF_NT_OPTIONAL64_HEADER

#else

#define IMAGE_SIZEOF_NT_OPTIONAL_HEADER     IMAGE_SIZEOF_NT_OPTIONAL32_HEADER

#endif

\sscli20\pal\win32\win32pal.h

Add #include <Vs9.h> after line 1272 (before the windows includes)

\sscli20\tools\binplace\sources; \sscli\clr\src\tools\ildbdump\sources

Change line 27 SUBSYSTEM_VERSION=4.00 to SUBSYSTEM_VERSION=5.00

\sscli20\tools\resourcecompiler\sources

Change line 31 SUBSYSTEM_VERSION=4.00 to SUBSYSTEM_VERSION=5.00

\sscli20\tools\cppmunge\sources

Change line 24 SUBSYSTEM_VERSION=4.00 to SUBSYSTEM_VERSION=5.00

\sscli20\tools\build\sources

Change line 48 SUBSYSTEM_VERSION=4.00 to SUBSYSTEM_VERSION=5.00

\sscli20\pal\win32\make.cmd

Kill the if not "%ROTOR_TOOLSET_VERSION%" block from line 43-46

\sscli20\clr\src\vm\sources.inc

Add -wd4800 to the end of line 22
Delete lines 23-25

\ssclie20\clr\src\classlibnative\nls\sources.inc

Add -wd4800 to the end of line 20

\sscli20\csharp\sccomp\sources.inc

Kill lines 52-54 (USER_C_FLAGS)

\sscli20\pal\win32\rotor_pal.src

Replace line 57 (#if _MSC_VER == 1400) with:

#if _MSC_VER == 1500

#define _MSVCRT MSVCR90D

#elif _MSC_VER == 1400

b. Replace line 67 (#if _MSC_VER == 1400) with:

#if _MSC_VER == 1500

#define _MSVCRT MSVCR90

#elif _MSC_VER == 1400

Well there you have it. Hopefully I didn't miss any of my changes or make too many typos. I ran through these instructions on a clean install of SSCLI and was able to successfully build per the docs and compile and run HelloWorld.