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.
Related
I need some help. I have put in dozens of hours into a VB.NET project, it has been built in release mode and distributed. Now I have to make some changes to it, and I am unable to debug it properly. My code changes result in behavior where my code is not even recognized.
Also, I installed Visual Studio 2013 recently (moving from 2010), but this project behaves the same in both environments.
I believe that my code has become 'optimized'. The error window tells me that code is being skipped over, and that my code is optimized and JIT is checked.
I have turned off JIT, and I have tried everything to make this project work again that I could think of. I am desperately wanting to know how I can get this project to be in a state where it will debug each line of code again when I make changes.
I can even purposely write bad code, and the debugger does not see it.
This project is now in debug mode, not release. I have checked and followed threads on every thing that other people have done to solve this issue, but nothing works for me.
Either my project launches and works properly as it is coded, or if I change any code only the form launches with no code being run - at all.
please help.
I finally figured it out. The applications that I was struggling with were all built in Visual Studio 2010 on Windows 10. I was trying to work with these in Visual Studio 2013 on Windows 7.
Once I tried to work with them on Windows 10 (visual Studio 2013 this time), they started working and debugging just fine.
I think it may have been DLL assembly paths? Took me more than a week, but I figured out my issue by moving from Win7x64 to Win10x64.
I have been trying using Pex in a F# project but I have faced several issues on which I would appreciate some help:
Visual Studio Pex addin worked for half an hour and not for complex project exploration.
After that each time I run a Pex Exploration from within Visual Studio 2010 I get a !warning! [metadata] no explorations found after applying all filters; did you forget a [PexClass] or [PexMethod] attribute? error message. If I copy and paste the command run by visual studio when doing the exploration and remove some attributes (like sourceFilter ...) and run it from a command console then I get some generated tests. Any idea why visual studio generates an invalid command?
After a while the Microsoft.Pex.Framework.dll either disappears from the .Net Reference list and I have to reference it manually using its file path or I can't even reference it any more and I have to uninstall/reinstall Pex. (A reference to C:\Program Files (x86)\Microsoft Moles\PublicAssemblie\Microsoft.Pex.Framework.dll could not be added. Please make sure that the file is accessible, and that it is a valid assembly or COM component.)
All these issues don't occur when I work on a C# project.
Issues 1 2 3 occurred with the Academic version.
Using the version available for MSDN Subscriber I never got it working within visual studio (Visual Studio 2010 Ultimate NO SP1). However it worked from the command prompt. I did not face problem 3 with this version.
Has anyone managed to get Pex working with F# within visual studio ? If yes can you you tell me how you did it ? Which versions (VS and Pex) do you use ?
I have had some success running Pex with F#. The version I used, if I believe my Downloads folder, was the academic version of Microsoft Pex and Moles 0.94.51006.1 Release for (x86). The installation file was named pex.academic.x86.msi.
I don't know if that version predates yours.
My impressions from my trials were that Pex and F# were not a very good combination: Pex insisted on creating test cases with null inputs. As generating null values in F# isn't all that common, that's typically not the scenarios in which I'm interested. Adding lots of assumptions to eliminate those just left me with Pex not being able to generate test cases. Admittedly, the functions I was testing were too complex, I still like the idea behind Pex and might try it again on smaller/easier pieces of code.
Using Pex and its GUI inside VS 2010 worked relatively fine, but not without frustration.
[Edited]
intellisense is not working just for just one XAML file in a particular solution (the solution compiles and runs fine) it works on every other project and other files.. can someone point me to instructions on how to fix it ?
I am using Visual studio 2010 express edition for windows phone.
I doubt this is the problem since you say it works in other projects, but Statement Completion for XAML might not be turned on in the options.
Either than that... I've had some weird problems with intellisense randomly not working at times. Most of the time deleting the intellisense database (.ncb file) so VS can rebuild it seems to work.
I'm used to using Idle for Python development, but decided to give Visual Studio 2010 + IronPython a try last week. It seems to work fine, but I noticed that triple-quoted (multi-line) strings don't highlight correctly in the editor. See photo:
Does anyone else have this problem or know of a good fix? Apart from that bug, Visual Studio seems to be great for Python.
This is a bug that is already fixed for the next release - I screwed up storing our state while processing line-by-line when fixing another bug.
If you're really anxious you can actually build the MSI which includes the tools from the sources on CodePlex. Once you have the VS SDK installed it should be as simple as running Scripts\Bat\Dev.bat to setup the enlistment environment and then msbuild Msi\Installer.proj which will produce an MSI in Bin\Debug.
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