FUTURE POSTS
- Partial writes, IO_Uring and safety - about one day from now
- Configuration values & Escape hatches - 4 days from now
- What happens when a sparse file allocation fails? - 6 days from now
- NTFS has an emergency stash of disk space - 8 days from now
- Challenge: Giving file system developer ulcer - 11 days from now
And 4 more posts are pending...
There are posts all the way to Feb 17, 2025
Comments
I loved this "free feature" already with Binsor and even more with the late RhinoETL. It's really a plus, when you're not sure what the code does and you want to do some deeper investigation.
I'm new on Boo. But it looks you're using Visual Studio to code, build and debug Boo. Am I correct?
What kind of package are you using for integration? Are you using http://developer.novell.com/wiki/index.php/Boo_language_package_for_Visual_Studio_2005 ?
I am using VS as a text editor in this case, no special packages.
When I need to do serious Boo work, I use #Developer
How do you make VS pick up the correct source file? the .pdb file includes that information?
You should better goes on…You guys are really inspirational
Yes, indeed
Yes, indeed
Is VS2005 doing the compilation for you? Is that just a pre-build event or something?
BooCompiler is doing the compilation.
In general, I would set it up with a booproj, so it is handled via MSBuild like the rest of the projects
Comment preview