Is there a way to use boo in my msvs? I would like my form to call some boo code instead of C#.
I'm using Boo to replace an old database-driven clunky rules engine, and it's working great.
Start here: Boo Interactive Interpreter
// One-line Boo interpreter in C#
InteractiveInterpreter2 interpreter = new InteractiveInterpreter2();
If you mean defining your forms and actually coding Boo in VS .NET, look into BooLangStudio.
We've been working on a plug-in for a while, it sorta works but you should really use SharpDevelop or MonoDevelop at this point. The VS plugin might get revitalized since the new VS plugin architecture for VS2010 is so much better but it's really a lot of work and we have all been pretty busy.
Visual Boo (source code) is a more recent project adding support for Boo in VS2010.
You can have your Boo script pop-up a source-readable VS debugger by inserting:
System.Diagnostics.Debugger.Launch()
or
System.Diagnostics.Debugger.Break()
If by msvs you mean visual studio, you would have to write a language plugin for boo (assuming one does not exist) using the Visual Studio Extendability framework.
Here is such a plugin :
http://www.codinginstinct.com/2008/05/boo-in-visual-studio.html
Related
I have created a coded UI test using visual studio , I got the code in VB and I need it in c# ,is there a way to convert it to c# using visual studio? or that I must do the coded UI process all over again ?
I had a similar problem last year where I was asked to recode a project from VB to C#. I ended up re-recording the entire project in C# since the Designer Files are computer generated, they can't be editted by the UI Tools if they're VB then converted to C#. It also gave the opportunity to redesign the tests in a more functional way.
I don't have VB test handy to check this, but you could try using a web based converter and go from there. Might be better than starting from scratch.
http://www.developerfusion.com/tools/convert/vb-to-csharp/
I'm going to school for computer programming and I have been using Xcode and really like its predictive text input (or whatever you call it maybe interpreter). The only thing is that it seems to function a little different when creating a C++ project. Such as you don't have to say "#include " to use the string library. Where as in Visual Studio you have to. What i'm afraid of is turning in a class project done on Xcode and missing including a lib and losing points. So i would like to do it on VS 2010 but i would like to have a better interpreter. Any help on this.
I think you mean AutoComplete..... and there is an add on called Visual Assist X that makes it magic for C++ coding.
I frequently find myself making a dummy console app to test something simple out. (For example how does DateTime.Parse like a YYYY-MM-DD-HH-MM-SS formatted string?)
I know that Roslyn has the C# interactive window to allow such simple tests to be run in the IDE with my solution still open. This is the only feature I am really wanting.
But how stable is Roslyn CTP? Is it going to mess up my IDE? Slow me down when I am not using it? Is it only used for the Roslyn features? Or is it going to try to replace my normal compiler for my open solution?
As SLaks says, the Roslyn CTP doesn't generally affect your IDE for existing scenarios. The changes you should see if you install it are:
A new C# Interactive tool window.
Support for "C# script" files (.csx), using the Roslyn IDE services. However, .cs and .vb files and projects still use the existing code.
Some new project templates for targeting Roslyn.
Some additional items in the Add References dialog for targeting Roslyn
Documentation, etc in the Roslyn directory under your My Documents folder.
Disclaimer: I work for Roslyn on the Roslyn project.
Unless you run VS with -rootSuffix Roslyn, the CTP will not change any existing behavior.
Try the C# REPL Script Environment that is part of the O2 Platform
It will give you a perfect environment to try out all C# features and APIs (conceptually the O2 REPL environment is similar to LinqPAD)
On the topic of Roslyn, take a look at these Multiple Roslyn based tools (all running Stand-Alone outside VisualStudio) , the first one is a simple Roslyn REPL
I just recently played with Rhino DSL and created a simple DSL using Boo. When I debugged my first code I was quite suprised to find out, that while debugging I was actually stepping through the boo file as well. That is awesome!
This was with Visual Studio 2008 Pro.
Now I switched my code to VS 2010 Pro ... and no more debugging in my Boo file :( What do I need to make VS 2010 step through my Boo file just like VS 2008 did?
OK, I got it - when I edit the boo-file and it get's re-compile while debugging I can step through the boo file. This works in VS2010 just the same as in VS2008. Obviuously I always modified my boo-file in VS2008; if I don't change the boo-file I also can't step through the file in VS2008.
Can I use LINQ within VS2005 if I have .NEt 3.5 installed?
The thing to remember is that at it's core Visual Studio, like any IDE, is a glorified text editor with an integrated debugger, and maybe a few other features as well. You could certainly use Visual Studio 2005 to input the code text of your linq program and then use the .Net 3.5 command line compiler to build it. You might even be able to find or write an add-in to automate the build process.
That means the technically correct answer to your question is, "Yes."
However, you won't get any extra IDE support:
Incorrect/broken intellisense.
Incorrect/broken syntax highlighting
Inability to work with .Net 3.5+ solution files.
No debugger support
The result is that you would probably be better served if I had simply said, "No."
If you already have 2005 but not 2008, you have a few options:
Get the 2008 Express Edition
Use a third-party tool like #Develop
Buy a 2008 full edition
There is no direct compiler support for LINQ in VS 2005.
You can still use the LINQ namespace and methods, however, it is not as elegant as using it in VS 2008.
See this article for details.
Vs2005 and C# do not directly support Extension Methods, Lambda Expression, Anonymous Types or Expression Trees which are key enabling features of LINQ. Some of the early LINQ betas did work with VS2005 and C# but none of the release products.
Likely the same for VB but I can't directly comment on VB other than I am about 99.99% sure you can't.
Simple answer is no.
LINQ relies on language features (such as extension methods) that VS2005 does not support.