# A couple of issues building in Visual Studio **URL:** \ **Category:** IronRuby\ **Created:** [October 15, 2007, 6:09am UTC](https://www.ruby-forum.com/t/a-couple-of-issues-building-in-visual-studio/117238 "2007-10-15T06:09:04Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Derek\_Knight](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/90ced4/32.png) [@Derek\_Knight](https://www.ruby-forum.com/u/Derek_Knight)\ **Post date:** [October 15, 2007, 6:09am UTC](https://www.ruby-forum.com/t/a-couple-of-issues-building-in-visual-studio/117238/1 "2007-10-15T06:09:04Z")
I posted this in the open-discussion forum. Maybe that’s not used much these days. ``` I've found a few problems building IronRuby on Windows (using the ``` IronRuby.sln file). It’s possible my set-up might be bad, although all I did was download the SVN files and build them. ``` A number of the projects have bad references (these look to be ``` caused by the projects not being in the location the csproj files expect). I found that I had to change the following CSPROJ files (Ruby, IronRuby.Libraries, ClassInitGenerator, Ruby.Console, RubyTestHost). ``` Also, I was doing a Release build and that does not compile. The ``` Microsoft.Scripting library has #if DEBUG round definitions of 2 Utils.ReflectionUtils functions (FormatTypeName and FormatTypeArgs), which are referred to in Program.cs of ClassInitGenerator. ``` I'm guessing others don't build from the Visual Studio solution ``` (or I’ve set my environment up stupidly). ``` Derek ``` ---
**Author:** ![Derek\_Knight](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/90ced4/32.png) [@Derek\_Knight](https://www.ruby-forum.com/u/Derek_Knight)\ **Post date:** [October 15, 2007, 3:23pm UTC](https://www.ruby-forum.com/t/a-couple-of-issues-building-in-visual-studio/117238/2 "2007-10-15T15:23:14Z")
I am able to build the source with [VS.NET](http://VS.NET) 2005. I don’t remember if there were any tricks that I had to do to make it work… Have you tried building with rake? -Eric ---
**Author:** ![Derek\_Knight](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/90ced4/32.png) [@Derek\_Knight](https://www.ruby-forum.com/u/Derek_Knight)\ **Post date:** [October 15, 2007, 3:50pm UTC](https://www.ruby-forum.com/t/a-couple-of-issues-building-in-visual-studio/117238/3 "2007-10-15T15:50:10Z")
Same here. I didn’t try the rake build - I just open the solution in VS2005 and build away - both debug and release mode. Derek - are you sure it’s the 2005 version? I saw the references problem last time I opened the 2008 solution, but didn’t have a chance to see what was going on. Cory From: removed\_email\_address@domain.invalid [[mailto:removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)] On Behalf Of Eric N. Sent: Monday, October 15, 2007 9:23 AM To: removed\_email\_address@domain.invalid Subject: Re: [Ironruby-core] A couple of issues building in Visual Studio I am able to build the source with [VS.NET](http://VS.NET)[http://VS.NET](http://VS.NET) 2005. I don’t remember if there were any tricks that I had to do to make it work… Have you tried building with rake? -Eric On 10/15/07, Derek Knight \ wrote: I posted this in the open-discussion forum. Maybe that’s not used much these days. I’ve found a few problems building IronRuby on Windows (using the IronRuby.sln file). It’s possible my set-up might be bad, although all I did was download the SVN files and build them. A number of the projects have bad references (these look to be caused by the projects not being in the location the csproj files expect). I found that I had to change the following CSPROJ files (Ruby, IronRuby.Libraries, ClassInitGenerator, Ruby.Console, RubyTestHost). Also, I was doing a Release build and that does not compile. The Microsoft.Scripting library has #if DEBUG round definitions of 2 Utils.ReflectionUtils functions (FormatTypeName and FormatTypeArgs), which are referred to in Program.cs of ClassInitGenerator. I’m guessing others don’t build from the Visual Studio solution (or I’ve set my environment up stupidly). Derek