Which IDE if any, are people using to develop Ironruby in?
If you are looking for an integrated Visual Studio editor, with intellisense etc, Microsoft has nothing in plan yet (according to this article with John Lam -> http://www.infoq.com/articles/state-of-ironruby). But there is an integrated editor which works pretty good - SappireSteel - at http://www.sapphiresteel.com/Ruby-In-Steel-For-IronRuby.
If you just want to edit in VS and don't care about intellisense and such, you could try and set up an external tool from within VS and call the ir.exe (http://msdn.microsoft.com/en-us/library/68c8335t%28VS.80%29.aspx)
There are numerous editors with support for ruby highlightning which you can try out as well, but there is no one (I think) with intellisense-like support for the .NET framework. Scite (http://www.scintilla.org/SciTE.html) is pretty popular, Scott Hanselman blogged about Ruby support/highlightning in Notepad2 (http://www.hanselman.com/blog/NewNotepad2WithRubySyntaxHighlighting.aspx). On Codeplex you can find a tool called IronEdit (http://www.codeplex.com/IronEditor) which I've not tried myself yet.
I ran RubyMine (http://www.jetbrains.com/ruby/index.html) for a while, which seems to be a really good Ruby IDE (costs money), but doesn't have any specific support for IronRuby. I hope the JetBrains will release something which plugs into Visual Studio eventually...
Personally I think Sapphire will come up with something really good eventually. I hope this helps.
I use Vim as my IDE with some custom settings that I blogged about some time ago.
Visual Studio?
According to the IronRuby website Visual Studio C# Express can be used (and in turn, any commercial version of Visual Studio 2005+ I'll assume).
From the IronyRuby.net home page:
Today, you must check the source code out of the IronRuby Subversion repository on Rubyforge. You will need a Subversion client: we recommend TortoiseSVN. To build the sources from the command line, you must also have Ruby installed on your computer already: we recommend the Ruby one-click installer. You can also build the sources using Visual Studio; if you don't already own a copy, you can download a free copy of Visual C# Express 2008.
Ruby in Steel from Sapphire Steel is build on the Visual Studio Shell (integrated mode) that will merge with Visual Studio 2008 if you already have it installed or simply be a standalone installation if you don't have Visual Studio already installed.
Also, no use to you, but Microsoft are going to be releasing IronRuby Studio (and IronPython Studio) at some point in the future. I couldn't find much about these on the web though - they were mentioned by a speaker at Teched Europe a few weeks ago.
You might interested in IronEditor. which similar to SciTE. get it at http://www.codeplex.com/IronEditor
Sapphire has a version now specifically targeted at IronRuby. Furthermore, not only is the alpha free now but they claim production will be free as well.
edit:forgot to include linkage
IronRuby integration in VS2010 can be found here: http://ironruby.net/tools/
The IronRuby tools are a good place to start but I think the best IDE for doing Ruby or in more detail Rails is VIM. by using a plugin such as rails.vim you can keep all your shortcuts and scripts across the boundaries such as Windows / Linux or IronRubyOnRails / RubyOnRails ...
JetBrains is offering a great IDE with RubyMine. I can remember that I've read an article about how to configure RubyMine to support IronRuby.
But as already mentioned IronRuby Tools for VS2010 are a good place to start.
The current version(s) of IronRuby now contain Ruby Tools for Visual Studio, which install along with IR itself. This is true for versions 1.1 and later.
Related
Is there any way I can use Nintendo TWL or Nitro SDK on Visual Studio, along with their IS-NITRO-DEBUGGER? I know there're some workaround, since I heard people using Visual Studio to work on DS/DSi games. I don't want to use CodeWarrior for this.
PS: I have Visual Studio 2010 and 2012 express edition.
It should be pretty easy, I wrote a little wizard that creates projects for use on the devkitPro toolchain (supports the DS among others) that could probably be modified for use with the official devkit. VS 10 is a bit more friendly with this sort of setup but it works on VS12 as well.
http://pern.drunkencoders.com/
The wizard is here and you will have to install it then open and edit the javascript files...no access to the official devkit so can't comment on how much of an undertaking this might be.
You may simply be able to edit the libnds template makefiles to point at the official toolchain and the wizard will just work as is (other than having to create a debug association).
There are also some good debugging tools if the toolchain that is based on gcc that will let you debug directly in visual studio with memory watches and custom viewers.
In our company, we have two main development environment. One uses VS2010 for C# and C++ development, the other uses Code Composer from TI (not the newest Eclipse based, and no, I cannot upgrade it right now).
Some of the C++ code is shared between VS solution and the embedded solution.
I'm in the process of upgrading our VSS to TFS, and so far everything is a bliss, but it is going to be a hard sell telling my EE engineers that they need to install VS2010 to perform source control.
I'm installing the TFS 2010 Power Tools right now, but the bad reviews scare me.
So, what's the best way to perform this integration?
You can get the engineers licensed with TFS and then use the explorer to have them check in and out, if Visual Studio scariness is the main issue. The explorer is very lightweight compared to Visual Studio.
As for the power pack, it is an installation on top of VS or the Explorer, unless you are talkinga bout TFPT.exe, which is a command line tool to be able to work with source code. I would not head that way, although engineers might be brainiac enought to love the DOS/UNIX like syntax. :-)
I got started with F# back in the day (before VS2010 beta); at the time, if I remember correctly, there was not an Express version of F#, but one could use the VS Shell (I think that was the name) and then install F# on top of it.
What's the current state of affairs? I've read out there that there's no 2010 Express version of F#; is there a 2010 Shell that one can download and install F# latest on top of? If not, what's the best way (if any) to code in F# 2010 for free?
I'm aware that asking for free stuff is A LOT to ask for. But this was possible in VS2008 and I'm wondering if it's also possible in VS2010.
Thanks!
PS - I believe (not sure though) that VS2010 beta can be downloaded for free; the problem with that is that when the final release comes out, one will have to pay for a license. For a guy who codes for fun like myself it doesn't make much sense to buy the full version if I can get the very basic features for free...
See
https://stackoverflow.com/questions/734525/getting-started-with-f
Basically right now you can use the free VS2008 integrated shell along with the F# CTP, or use the VS2010RC (which is free as a Beta).
(I don't know if there is a VS2010 shell published yet, and I don't know if the F# CTP works with it; for the moment, your best long-term-free strategy is to use 2008.)
I think you can also use SharpDevelop with F#:
http://www.icsharpcode.net/OpenSource/SD/Features.aspx
If you mean visual F# the best tool is Visual Studio 2010 RC:
Check out these links :
Creating Your First F# Program with Visual Studio
Using Visual F# to Create, Debug, and Deploy an Application
**[Update]**Check out this link too:Features of the Visual Studio 2010 Release of Visual F#
I am new to win32 programming and also to driver programming. I have installed Windows DDK on my system and have got some examples with the DDK but those examples don't have dsw file.
I wanted to know how can I create .dsw file so that I can open that workspace in VC6.
Most people who build DDK/WDK projects in Visual Studio do so using a 'makefile' project that invokes the DDK's build.exe utility. This works quite well- you get the code navigation capabilities of Visual Studio while building your DDK project using the standard, supported DDK tools.
Note that the DDK comes with it's own set of compilers, and those compilers should be used to build DDK projects.
OSR has a little set of cmd scripts that is supposed to make this easier (it's been years since I've done anything with those; I really can't remember how well they work):
http://www.osronline.com/article.cfm?article=43
Another similar tool is available from Hollis Technology:
http://www.hollistech.com/Resources/ddkbuild/ddkbuild.htm
As far as debugging goes, unfortuantely the VS debugger won't work for kernel mode driver debugging. For that, get the Debugging Tools for Windows package which has a great set of debuggers. The GUI debugger, WinDbg, is quite nice even if it's not quite up to the usability of Visual Studio's. And the documentation with the Debugging Tools is outstanding - you can learn a lot about Windows internals just by reading the WinDbg docs.
The last time I looked (which was years ago), you don't build device drivers using the Visual Studio IDE: the DDK has its own build.exe utility (similar idea but not the same as makefiles); and apparently this is still true as of early 2008, see for http://groups.google.com/group/microsoft.public.development.device.drivers/browse_thread/thread/4382c9b66f8611e9?pli=1
I expect that "how to build" is described in the DDK documentation.
I think better you integrate with Visual Studio 2005, 2008 or 2010 with this tool:
http://visualddk.sysprogs.org/versions/1.5.6
ChrisW is correct, you can't use Visual Studio (unless there is a way to set it).
Anyway, for start debugging you can use DebugView to print simple messages with DbgPrint.
VC6 is very old these days, can't you use a newer version? Anyway, as I recall, you can just open the project file as a workspace, the IDE will create the .dsw file for you.
Our company is considering using the Visual Studio Shell for one of our products.
Does anyone have any experience using it? Was it easy to work with? Did it save time? Are there any things that you weren't able to get it to do? Have you shipped anything with it?
A couple of points regarding the Isolated shell.
As you might know, there are two considerations when you use shell - Isolated Mode and Integrated Mode. (Read more from MSDN)
Isolated Shell can be used by organizations, to build applications that run side by side with other editions of Visual Studio.
Here are some points we learned,
trying to use shell for some of our
applications.
If you are planning to use Isolated
shell, you can't use Microsoft
Language Packages like C# and VB.NET
inside that.
Creating a package for your shell is
much like creating any other VS
Package.
You don't have support for Team
Explorer and VS Built in Source
Control access, in Isolated Shell
(See this post from Vin)
Though not directly related - If you are using VS SDK 1.1 to develop your packages - remember that the managed package framework is no longer available with the default distribution. So don't get surprised if your old packages can't load MPF files after moving to SDK 1.1. It has got moved to Codeplex as a separate download.
I played around a bit with it a couple of weeks ago, like every thing there is going to be a learn curve but if you study the examples a bit and have a look at a project on codeplex called Storyboard designer. I'm sure that you could pick it up, I found it very hard to find other examples on the net but I wasn't looking very hard.
I would say if you think that the shell can give you want you need I would go for it, it is a very handy interface to work with and if your targeting developers it is also a common interface for them, so it will feel natural.
I typically use Visual Studio Community on my PC for developing business intelligence solutions (databases, SSIS, SSAS, SSRS), then deploying to the server. A few weeks ago my managers requested we put Visual Studio on a server so that other developers and consultants could connect to the server and access Visual Studio.
Ultimately I installed SQL Server Data Tools (14.0.61021.0), which automatically installed Visual Studio Shell 2015. After installation, I launched Visual Studio Shell and tried doing some of the things I am used to doing in Community edition. I was able to do pretty much anything I was used to doing for BI Development.
Visual Studio Shell 2015:
Solution files with BI projects...
SSIS
Installing extensions & add-ons...
ANKHSVN for version control with SVN server
Visual Studio 2015 Color Theme Editor
Project deployment