Common Compiler Infrastructure - Sample applications

Commented Issue: CCISharp No Longer builds [6786]

hermanv — Tue, 21 Feb 2012 18:46:03 GMT

CCISharp no longer builds on a clean check either in VS2010 or using build.cmd.

The main culprit seems to be Microsoft.Contracts (.NET 2 project), which conflicts with the System.Diagnostics namespace in .NET 4.

Framework has to be migrated from .NET 2 to .NET 4 as CCI itself is now in .NET 4, which then causes it to fail due to the issue above.

Removing Microsoft.Contracts will largely fix these issues.

However the next issue was:
error CS0618: Warning as Error: 'Microsoft.Cci.MutableCodeModel.Contracts.CodeAndContractMutatingVisitor' is obsolete: 'Please use CodeAndContractRewriter'

Resolving this is a much bigger problem as there appears to be quite a fundamental change and I'm not confident enough in the framework yet to make the change myself. I could however set it to treat the warning as a warning and ignore the obsolescence but at this point I figured it was better to raise the issue and point out the sample is currently unusable.

Thanks.
Comments: ** Comment from web user: hermanv **

I've fixed the build breaks. Adapting CCISharp to use the more modern visitors and mutators will have to wait for Peli to come back from vacation. There is also an issue with the test assembly which runs the code contracts rewriter when it builds, but the rewriter fails for some reason. I do not yet understand this issue.

Source code checked in, #67966

hermanv — Tue, 21 Feb 2012 18:42:12 GMT

Fix build.

Created Issue: CCISharp Nuget [6787]

thargy — Tue, 21 Feb 2012 11:15:09 GMT

Creating CCISharp as a Nuget is fairly trivial and would massively increase it's adoption. There are some gotchas around install/uninstall scripts that I'm happy to help resolve (I've had to resolve them in my own rewriters).

The whole framework would be +1 if the CCI core itself was built into a Nuget as well.

There are real issues with Nuget production, but when it comes to ease of use for the end user it makes things really easy.

Happy to help if I can get CCISharp to build.

Created Issue: CCISharp No Longer builds [6786]

thargy — Tue, 21 Feb 2012 11:11:04 GMT

New Comment on "How do I CciSharp"

thargy — Tue, 21 Feb 2012 11:00:12 GMT

All the issues appear to be around the inclusion of Code Contracts into the BCL causing conflicts with the .NET 2 Microsoft.Contracts project.

New Comment on "How do I CciSharp"

thargy — Tue, 21 Feb 2012 10:41:46 GMT

Neither opening in VS2010 and building, or build.cmd work on a clean check out any more.

New Post: books about CCI

hermanv — Thu, 18 Aug 2011 02:13:10 GMT

There aren't any books that cover CCI. The basic concepts are in most compiler books. One book that I know of and that talks specifically about .NET compilers is Compiling for the .NET Common Language Runtime (CLR) by John Gough.

New Post: books about CCI

keithwanta — Thu, 18 Aug 2011 02:08:45 GMT

What is the best resource/book to learn about the concepts of compilers, that would explain concepts closely related to the CCI framework and CciSharp?

New Post: CCI samples (source) solution not creating dll files

keithwanta — Mon, 08 Aug 2011 04:22:38 GMT

This CCI project is incredible! I've only been doing .NET development full time for 6 months now. I stumbled upon this site when I was reading about System.Reflection on Friday and have spent 15 hours looking at this code all weekend. I must be a geek! :-)

New Post: CCI samples (source) solution not creating dll files

hermanv — Mon, 08 Aug 2011 03:28:22 GMT

I've deleted the downloads and changed the text as suggested.

Updated Wiki: How do I?

hermanv — Mon, 08 Aug 2011 03:27:04 GMT

How do I

Build a CCI sample application

First install TortoiseSVN on your PC. Then go to the Source Code tab (in the http://ccisamples.codeplex.com site). Then click on the "connection instructions" hyperlink under the "Source Control" section and use that SVN path for the SVN checkout option. Once you've checked out the code for the ccisamples project, open a sample solution in the root directory of the source tree (for example, SmallBasic.sln). Now just get Visual Studio to build the solution (I like to hit the build solution button). It is that easy.

If you want to use the CCI components in a solution that lives in another CodePlex project, or another Subversion repository, simply use the svn:external property to set up a link between the two repositories, and then add the relevant CCI projects to your solution. This technique has been used to make this CodePlex project (ccisamples) import the separate cciast, ccimetadata and xunit CodePlex projects.

Execute the test suite

CCI uses the xUnit.net test framework to execute the test suite. With just Visual Studio installed, the test projects are set up to use the basic xUnit.net runner but there are alternative runners that provide a smoother Visual Studio integration. These include:

Gallio (open source)
TestDriven .NET (To enable this for xunit, run the xunit.installer project in the Xunit\Main directory.)
Resharper

New Post: CCI samples (source) solution not creating dll files

keithwanta — Mon, 08 Aug 2011 02:38:17 GMT

Thanks Herman. No, I did not see those instructions easily visible.

Can you tell me what this code is (and how old it is)? Should we not use this code?
Downloads tab > click "Latest Build" hyperlink (right side of page) > click on "Sources" hyperlink > click "I Agree" button

To a new person visiting the site, a lot of assumptions need to be made for these instructions. I guess a typical person viewing the site is concentrated on the Download tab. It just confused me.

I think it would be clearer if you changed the instructions from this:

Go to the Source Code tab and make sure that you have TortoiseSVN installed. Then simply check out the ccisamples project and open a sample solution in the root directory of the source tree (for example, SmallBasic.sln). Now just get Visual Studio to build the solution (I like to hit the build solution button). It is that easy.

If you want to use the CCI components in a solution that lives in another CodePlex project, or another Subversion repository, simply use the svn:external property to set up a link between the two repositories, and then add the relevant CCI projects to your solution. This technique has been used to make this CodePlex project (ccisamples) import the separate cciast, ccimetadata and xunit CodePlex projects.

To this:

If you want to use the CCI components in a solution that lives in another CodePlex project, or another Subversion repository, simply use the svn:external property to set up a link between the two repositories, and then add the relevant CCI projects to your solution. This technique has been used to make this CodePlex project (ccisamples) import the separate cciast, ccimetadata and xunit CodePlex projects.

New Post: CCI samples (source) solution not creating dll files

hermanv — Mon, 08 Aug 2011 01:08:32 GMT

Did you read this: http://ccisamples.codeplex.com/wikipage?title=Before%20you%20download%20the%20sources%2c%20READ%20THIS&referringTitle=Home ?

AST stands for Abstract Syntax Tree.

New Post: CCI samples (source) solution not creating dll files

keithwanta — Mon, 08 Aug 2011 00:55:34 GMT

Today I downloaded the source code samples for CCI, and noticed that some of the code didn't compile when I compiled the entire solution. For example, under the .\Ast\Metadata\Sources\ folder, there were several folders. In Visual Studio, Metadata shows as a folder, and under that folder, there are several namespaces/assemblies. However, these namespaces/assemblies didn't seem to create a dll when I built the entire solution. They don't even appear to be under a *.csproj file, so I'm guessing I need to do that manually to create a dll or put this code into my own code, yes? I see the references to the actual CCI framework throughout, but didn't see these samples being compiled. Were they supposed to create dll files, or are they not being compiled into namespaces because they are merely samples and showing how they can be used? If that's the case, that's fine. But I thought i was missing something. If someone can point me to the documentation of this source code, and describe how the files in this solution are laid out, that would be great.

Also, I downloaded the binaries for CCISharp earlier. Then I used .NET Reflection to see what the CCISharp was all about because I couldn't find the source code for it. When I looked at it, it seemed completely different from the source code described in my previous paragraph. What code paths in the solution described above are supposed to be part of CCISharp?

One other question :-) What does AST stand for?

Thanks in advance.

Source code checked in, #64374

pelikhan — Thu, 28 Jul 2011 21:34:48 GMT

fixed potential null dereference

Source code checked in, #64373

pelikhan — Thu, 28 Jul 2011 21:29:41 GMT

using CodeDeepCopier instead of CodeCopier to avoid losing decompiled method bodies

Source code checked in, #64366

pelikhan — Thu, 28 Jul 2011 05:23:49 GMT

a couple fixees to ccisharp

Source code checked in, #64365

pelikhan — Thu, 28 Jul 2011 05:04:03 GMT

fixed compilation issue

Commented Issue: HelloIL sample throws NullReferenceException [6314]

hermanv — Tue, 26 Jul 2011 02:10:45 GMT

HelloIL sample throws NullReferenceException.

To fix it I added following property assignment to NamespaceTypeDefinition() instance creating code:
BaseClasses = new List<ITypeReference>(),
Comments: ** Comment from web user: hermanv **

Thanks. This is fxed now.

Commented Issue: Compilation error [6322]

hermanv — Tue, 26 Jul 2011 02:03:53 GMT

While compilation I got following error :
Failed to locate attribute "AssemblyVersion" in file "<mypath>\Ast\Sources\CodeModel\Properties\AssemblyInfo .cs"

I got the error on compilation of all projects used separate Build\version.cs file

How to fix to problem?
Comments: ** Comment from web user: hermanv **

The solutions in ccisamples.codeplex.com did not build for me either because of changes in CCI itself. I've fixed things so that they build again, but it is not clear to me that those problems would have caused they error you are seeing. Nevertheless, please try again and let me know if you are still seeing the problem.