BooLangStudio Wiki & Documentation Rss Feed

Updated Wiki: Home

justinc — Fri, 22 Aug 2008 20:20:42 GMT

Project Description
Do you like boo? Do you like Visual Studio 2008? Well, then you should like BooLangStudio!

About BooLangStudio

BooLangStudio is a VSIP for Visual Studio 2008 Standard Editition and up. It adds support for the Boo language to Visual Studio. It is released under the terms of the Microsoft Public Licnese (Ms-PL).

BooLangStudio is currently distributed as an Alpha release install.

Source Control

BooLangStudio is kept under source control via git and is available at:
http://github.com/olsonjeffery/boolangstudio/tree/master

Updated Wiki: Home

justinc — Fri, 22 Aug 2008 20:19:35 GMT

Project Description
Do you like boo? Do you like Visual Studio 2008? Well, then you should like BooLangStudio!

About BooLangStudio

Source Control

BooLangStudio is kept under source control via git and is available at:
http://github.com/olsonjeffery/boolangstudio/tree/master

Updated Wiki: Home

olsonjeffery — Fri, 22 Aug 2008 15:55:31 GMT

Project Description
Do you like boo? Do you like Visual Studio 2008? Well, then you should like BooLangStudio!

About BooLangStudio

BooLangStudio is a VSIP for Visual Studio 2008 Stanard Editition and up that adds support for the Boo language to Visual Studio. It is released under the terms of the Microsoft Public Licnese (Ms-PL).

BooLangStudio is currently distributed as a VSIP for the Experimental Hive, which means you need to have Visual Studio 2008 Standard Edition or greater and the Visual Studio 2008 installed. There are plans to obtain a PLK for the package in the near future, so that it can be distributed and target the "main" registry hive for Visual Studio 2008.

Source Control

BooLangStudio is kept under source control via git and is available at:
http://github.com/olsonjeffery/boolangstudio/tree/master

UPDATED WIKI: BooLangStudioScreenshots

olsonjeffery — Tue, 20 May 2008 17:58:24 GMT

BooLangStudio Screenshots

Version 0.1.1

Here is the basic view of BooLangStudio in action:

Here is BooLangStudio showing a build error:

UPDATED WIKI: BooLangStudioScreenshots

olsonjeffery — Tue, 20 May 2008 17:56:48 GMT

BooLangStudio Screenshots

Version 0.1.1

UPDATED WIKI: Home

olsonjeffery — Tue, 20 May 2008 17:56:22 GMT

Project Description
Do you like boo? Do you like Visual Studio 2008? Well, then you should like BooLangStudio!

About BooLangStudio

Want to see pictures of BooLangStudio in action? Check out BooLangStudioScreenshots.
BooLangStudioInstallInstructions
If you would like to learn the motivation behind BooLangStudio, please read WhyBooLangStudio.
If you're interested in knowing who is responsible for the various components of BooLangStudio, please read BooLangStudioAttributions.
See the BooLangStudioCHANGELOG.
A link to the Ms-PL: http://www.opensource.org/licenses/ms-pl.html.
And, of course, the TODOList (maybe to be replaced by the IssueTracker in the future).

Source Control

BooLangStudio is kept under source control via git and is available at:
http://github.com/olsonjeffery/boolangstudio/tree/master

UPDATED WIKI: BooLangStudioAttributions

olsonjeffery — Mon, 19 May 2008 21:48:58 GMT

Who-coded-what in BooLangStudio:

BooLangStudio contributor(s):

Jeff Olson - olson.jeffery@gmail.com

The stuff that helped make BooLangStudio possible:

RegisterMsBuildTargetsAttribute class (in BooLangStudio project): Based on the ProvideMSBuildTargetAttribute class in IronPython Studio, re-implemented by Jeff Olson
ProjectBase stuff: Source code linked from the Microsoft Visual Studio 2008 SDK ... I wish there were an easier way besides linking to the source, but this is the "pattern" that the MPF people came up with. Better than nothing.
Boo deps: Rodrigo B. de Oliveira and the Boo team, except:

Changes to BooLexer.cs (post-code generation from grammar) to make it play nice w/ an IDE by Jeff Olson
Overload to BooParser.CreateBooLexer() by Jeff Olson

Please let someone associated with BooLangStudio know if anything is misattributed/anything is missing.

UPDATED WIKI: BooLangStudioAttributions

olsonjeffery — Mon, 19 May 2008 21:48:40 GMT

Who-coded-what in BooLangStudio:

BooLangStudio contributor(s):

Jeffery Olson - olson.jeffery@gmail.com

The stuff that helped make BooLangStudio possible:

RegisterMsBuildTargetsAttribute class (in BooLangStudio project): Based on the ProvideMSBuildTargetAttribute class in IronPython Studio, re-implemented by Jeff Olson
ProjectBase stuff: Source code linked from the Microsoft Visual Studio 2008 SDK ... I wish there were an easier way besides linking to the source, but this is the "pattern" that the MPF people came up with. Better than nothing.
Boo deps: Rodrigo B. de Oliveira and the Boo team, except:

Changes to BooLexer.cs (post-code generation from grammar) to make it play nice w/ an IDE by Jeff Olson
Overload to BooParser.CreateBooLexer() by Jeff Olson

Please let someone associated with BooLangStudio know if anything is misattributed/anything is missing.

UPDATED WIKI: BooLangStudioAttributions

olsonjeffery — Mon, 19 May 2008 21:47:52 GMT

Who-coded-what in BooLangStudio:

BooLangStudio contributor(s):

Jeffery Olson (olson.jefferyATgmail.com)

The stuff that helped make BooLangStudio possible:

RegisterMsBuildTargetsAttribute class (in BooLangStudio project): Based on the ProvideMSBuildTargetAttribute class in IronPython Studio, re-implemented by Jeff Olson
ProjectBase stuff: Source code linked from the Microsoft Visual Studio 2008 SDK ... I wish there were an easier way besides linking to the source, but this is the "pattern" that the MPF people came up with. Better than nothing.
Boo deps: Rodrigo B. de Oliveira and the Boo team, except:

Changes to BooLexer.cs (post-code generation from grammar) to make it play nice w/ an IDE by Jeff Olson
Overload to BooParser.CreateBooLexer() by Jeff Olson

Please let someone associated with BooLangStudio know if anything is misattributed/anything is missing.

UPDATED WIKI: BooLangStudioAttributions

olsonjeffery — Mon, 19 May 2008 21:47:18 GMT

Who-coded-what in BooLangStudio:

BooLangStudio contributor(s):

Jeffery Olson (olson.jefferyATgmail.com)

The stuff that helped make BooLangStudio possible:

RegisterMsBuildTargetsAttribute class (in BooLangStudio project): Based on the ProvideMSBuildTargetAttribute class in IronPython Studio, re-implemented by Jeff Olson
ProjectBase stuff: Source code linked from the Microsoft Visual Studio 2008 SDK ... I wish there were an easier way besides linking to the source, but this is the "pattern" they're forcing us to use.
Boo deps: Rodrigo B. de Oliveira and the Boo team, except:

Changes to BooLexer.cs (post-code generation from grammar) to make it play nice w/ an IDE by Jeff Olson
Overload to BooParser.CreateBooLexer() by Jeff Olson

Please let someone associated with BooLangStudio know if anything is misattributed/anything is missing.

UPDATED WIKI: BooLangStudioAttributions

olsonjeffery — Mon, 19 May 2008 21:46:19 GMT

Who-coded-what in BooLangStudio:

BooLangStudio contributor(s):

Jeffery Olson (olson.jefferyATgmail.com)

The stuff that helped make BooLangStudio possible:

RegisterMsBuildTargetsAttribute class (in BooLangStudio project): Based on the ProvideMSBuildTargetAttribute class in IronPython Studio, re-implemented by Jeff Olson
ProjectBase stuff: Source code linked from the Microsoft Visual Studio 2008 SDK ... I wish there were an easier way besides linking to the source, but this is the "pattern" they're forcing us to use.
Boo deps: Rodrigo B. de Oliveira and the Boo team
Changes to BooLexer.cs (post-code generation from grammar) to make it play nice w/ an IDE by Jeff Olson
Overload to BooParser.CreateBooLexer() by Jeff Olson

Please let someone associated with BooLangStudio know if anything is misattributed/anything is missing.

UPDATED WIKI: BooLangStudioAttributions

olsonjeffery — Mon, 19 May 2008 21:45:38 GMT

Who-coded-what in BooLangStudio:

BooLangStudio contributor(s):

Jeffery Olson (olson.jefferyATgmail.com)

RegisterMsBuildTargetsAttribute class (in BooLangStudio project): Based on the ProvideMSBuildTargetAttribute class in IronPython Studio, re-implemented by Jeff Olson

ProjectBase stuff: Source code linked from the Microsoft Visual Studio 2008 SDK ... I wish there were an easier way besides linking to the source, but this is the "pattern" they're forcing us to use.

Boo deps: Rodrigo B. de Oliveira and the Boo team

Changes to BooLexer.cs (post-code generation from grammar) to make it play nice w/ an IDE by Jeff Olson

Overload to BooParser.CreateBooLexer() by Jeff Olson

Please let someone associated with BooLangStudio know if anything is misattributed/anything is missing.

UPDATED WIKI: BooLangStudioAttributions

olsonjeffery — Mon, 19 May 2008 21:45:19 GMT

Who-coded-what in BooLangStudio:

BooLangStudio contributor(s):
Jeffery Olson (olson.jefferyATgmail.com)

RegisterMsBuildTargetsAttribute class (in BooLangStudio project): Based on the ProvideMSBuildTargetAttribute class in IronPython Studio, re-implemented by Jeff Olson

ProjectBase stuff: Source code linked from the Microsoft Visual Studio 2008 SDK ... I wish there were an easier way besides linking to the source, but this is the "pattern" they're forcing us to use.

Boo deps: Rodrigo B. de Oliveira and the Boo team

Changes to BooLexer.cs (post-code generation from grammar) to make it play nice w/ an IDE by Jeff Olson

Overload to BooParser.CreateBooLexer() by Jeff Olson

Please let someone associated with BooLangStudio know if anything is misattributed/anything is missing.

UPDATED WIKI: BooLangStudioAttributions

olsonjeffery — Mon, 19 May 2008 21:44:12 GMT

Who-coded-what in BooLangStudio:

BooLangStudio contributor(s):
Jeffery Olson (olson.jefferyATgmail.com) blog

RegisterMsBuildTargetsAttribute class (in BooLangStudio project): Based on the ProvideMSBuildTargetAttribute class in IronPython Studio, re-implemented by Jeff Olson

ProjectBase stuff: Source code linked from the Microsoft Visual Studio 2008 SDK ... I wish there were an easier way besides linking to the source, but this is the "pattern" they're forcing us to use.

Boo deps: Rodrigo B. de Oliveira and the Boo team

Changes to BooLexer.cs (post-code generation from grammar) to make it play nice w/ an IDE by Jeff Olson

Overload to BooParser.CreateBooLexer() by Jeff Olson

Please let someone associated with BooLangStudio know if anything is misattributed/anything is missing.

UPDATED WIKI: BooLangStudioAttributions

olsonjeffery — Mon, 19 May 2008 21:43:53 GMT

Who-coded-what in BooLangStudio:

BooLangStudio contributor(s):
Jeffery Olson (olson.jefferyATgmail.com) [blog|url:http://olsonjeffery.blogspot.com]

RegisterMsBuildTargetsAttribute class (in BooLangStudio project): Based on the ProvideMSBuildTargetAttribute class in IronPython Studio, re-implemented by Jeff Olson

ProjectBase stuff: Source code linked from the Microsoft Visual Studio 2008 SDK ... I wish there were an easier way besides linking to the source, but this is the "pattern" they're forcing us to use.

Boo deps: Rodrigo B. de Oliveira and the Boo team

Changes to BooLexer.cs (post-code generation from grammar) to make it play nice w/ an IDE by Jeff Olson

Overload to BooParser.CreateBooLexer() by Jeff Olson

Please let someone associated with BooLangStudio know if anything is misattributed/anything is missing.

UPDATED WIKI: WhyBooLangStudio

olsonjeffery — Mon, 19 May 2008 21:39:51 GMT

Why Have Something Like BooLangStudio?

For many, many moons, Boo has languished in relative obscurity while other, more popular yet less capable (a subjective opinion, here) languages have dominated the discourse in the space of .NET coding best practices. And why? Because of the tyranny of programmers and their managers who are unwilling to venture outside of the scope of tools considered "mainstream", for whatever reason. Many times I have personally heard the excuse that Boo was not an option simply because you would have to install another IDE to actually use it.

Well, now you have one less excuse to not try Boo.

Boo is a truely awesome language, in my opinion. And while I'm perfectly comfortable working with Boo in the confines of #dev (or scribes in loonix), I feel that now is the time to bring Boo "into the fold". I also hope that BooLangStudio will put increased scrutiny on the Boo language from a stability/feature perspective. Being an open source project, an increased user load on Boo will have the benefit of bringing to the surface more issues with the language/compiler itself in more timely fashion, which is something you can only hope to get from the C# team in three-year product release cycles. I'm sure the maintainers of Boo won't be thanking me for the increased harassment they must endure, but I consider this tough love.

The 'boolang' google group is an excellent resource for news/information about the language/compiler/community. Since Boo has official releases fairly infrequently, yet most changes to the compiler/language are initiated on the mailing list, it's a great place to keep up to date on the goings-on of the Boo community. Please write to this group with issues CONCERNING THE BOO LANGUAGE/COMPILER ITSELF. Any other issues (that is, those relating to the greatness/suckiness of BooLangStudio) should be discussed on the BooLangStudio CodePlex site. While I won't apologize to the keepers of Boo for any increased scrutiny of bugs in the language/compiler, it'd be pretty stupid to spam them with issues about code (BooLangStudio) that they aren't responsible for.

BooLangStudio is released under the terms of the Microsoft Public-License (Ms-PL). I decided to choose this license, which is pretty much a re-branded Apache License 2.0. Hopefully a swarm of lawyers will not descend upon me.

BooLangStudio uses a slightly modified version of Boo.Lang.Parser.dll (small changes to BooParser and BooLexer to make it more friendly for use in an IDE). The changes to Boo.Lang.Parser are distributed in bin form (Boo.Lang.Parser.dll) for use by BooLangStudio and as source along with BooLangStudio. The actual Boo components are kept discreetly seperated from BooLongStudio. Anyone from the Boo community is free to integrate these changes back into the Boo code (although I doubt you would want to, it's quite kludge-tastic). Hopefully a swarm of Richard M. Stallmans will not descend upon me.

BooLangStudio is still pretty rough around the edges, and for this I apologize. I've basically "pulled myself up by the bootstraps" in terms of implementing a Visual Studio Integration Package from scratch with no prior knowledge of best/worst practices. I hope you will forgive me.

Despite this, I stand on the shoulder of giants. I have many people/projects to thank:

I'd like to thank Chris Bilson for putting the bug in my ear to implement this and managing to feign interest in the project for as long as he has.

Hilton Giesenow and Dylan Miles have an excellent series of videos on the MSDN site concerning VSIP. I would also like to thank Mr. Giesenow for his assistance via email with issues I had getting this project off the ground.

The IronPython Studio project has been a great source of inspiration and knowledge on how to implement a LanguageService/ProjectFactory/etc properly.

Also, the ManagedBabel example project and the various bits of example code in the VS 2008 SDK has been of immeasurable value to me in the process of implementing BooLangStudio and the larger task of grokking VSIP in the confines of the Managed Package Framework.

Many, many thanks go to Rodrigo B. de Oliveira for making a language as great as Boo. Thanks also to the developers who tirelessly hack away on the Boo source code and, more importantly, endure an endless stream of questions on the mailing list.

And last, but most certainly not least: Thanks to those co-users of Boo already out there in the wild, without whom Boo would just be Yet Another Programming Language.

In closing, if you're a new to the world of programming with Boo: Welcome! I hope you enjoy your stay. Please don't blame Boo (as a language) for any of the crappyness of BooLangStudio. It's actually written in C#.

If you're a longtime Boo user: Finally, we get to sit at the grown-up's table. If you're as big a fan of Boo as I, then here's to hoping you get to do more work in your language of choice :)

Sincerely,
Jeff Olson

UPDATED WIKI: Home

olsonjeffery — Mon, 19 May 2008 21:39:03 GMT

Project Description
Do you like boo? Do you like Visual Studio 2008? Well, then you should like BooLangStudio!

About BooLangStudio

BooLangStudioInstallInstructions
If you would like to learn the motivation behind BooLangStudio, please read WhyBooLangStudio.
If you're interested in knowing who is responsible for the various components of BooLangStudio, please read BooLangStudioAttributions.
See the BooLangStudioCHANGELOG.
A link to the Ms-PL: http://www.opensource.org/licenses/ms-pl.html.
And, of course, the TODOList (maybe to be replaced by the IssueTracker in the future).

Source Control

BooLangStudio is kept under source control via git and is available at:
http://github.com/olsonjeffery/boolangstudio/tree/master

UPDATED WIKI: Home

olsonjeffery — Thu, 15 May 2008 19:41:32 GMT

Project Description
Do you like boo? Do you like Visual Studio 2008? Well, then you should like BooLangStudio!

About BooLangStudio

BooLangStudioInstallInstructions
If you would like to learn the motivate behind BooLangStudio, please read WhyBooLangStudio.
If you're interested in knowing who is responsible for the various components of BooLangStudio, please read BooLangStudioAttributions.
See the BooLangStudioCHANGELOG.
A link to the Ms-PL: http://www.opensource.org/licenses/ms-pl.html.
And, of course, the TODOList (maybe to be replaced by the IssueTracker in the future).

Source Control

BooLangStudio is kept under source control via git and is available at:
http://github.com/olsonjeffery/boolangstudio/tree/master

UPDATED WIKI: Home

olsonjeffery — Thu, 15 May 2008 19:40:25 GMT

Project Description
Do you like boo? Do you like Visual Studio 2008? Well, then you should like BooLangStudio!

About BooLangStudio

BooLangStudioInstallInstructions
If you would like to learn the motivate behind BooLangStudio, please read WhyBooLangStudio.
If you're interested in knowing who is responsible for the various components of BooLangStudio, please read BooLangStudioAttributions.
See the BooLangStudioCHANGELOG.
A link to the Ms-PL: http://www.opensource.org/licenses/ms-pl.html.
And, of course, the TODOList (maybe to be replaced by the IssueTracker in the future).

Source Control

BooLangStudio is kept under source control via git and is available at:
http://github.com/olsonjeffery/boolangstudio/tree/master

UPDATED WIKI: Home

olsonjeffery — Thu, 15 May 2008 19:32:59 GMT

Project Description
Do you like boo? Do you like Visual Studio 2008? Well, then you should like BooLangStudio!

About BooLangStudio

BooLangStudioInstallInstructions
If you would like to learn the motivate behind BooLangStudio, please read WhyBooLangStudio.
If you're interested in knowing who is responsible for the various components of BooLangStudio, please read BooLangStudioAttributions.
See the BooLangStudioCHANGELOG.
A link to the Ms-PL: http://www.opensource.org/licenses/ms-pl.html.
And, of course, the TODOList (maybe to be replaced by the IssueTracker in the future).

Source Control

BooLangStudio is kept under source control via git and is available at:
http://github.com/olsonjeffery/boolangstudio/tree/master