One thing I like about Java vs. C# is that the source is available for all the recent versions of Java. So, if a system library is doing something counter-intuitive you can just dig in and find out why.
Comments are closed.
One thing I like about Java vs. C# is that the source is available for all the recent versions of Java. So, if a system library is doing something counter-intuitive you can just dig in and find out why.
Comments are closed.
Exactly. Getting sources downloaded for dependencies and the java class libraries is step number one for setting up a new maven pom. I now completely dread the Source Not Found page in Eclipse. 🙂
Huh, it looks like the main .NET libraries are supposed to have source available, but it’s just difficult if you have security patches installed…
http://stackoverflow.com/questions/8139269/how-to-enable-enable-net-framework-source-stepping
Argh, confirmed. Patches are the problem. From http://blogs.msdn.com/b/sburke/archive/2008/01/16/configuring-visual-studio-to-debug-net-framework-source-code.aspx
“What happens if I download a Hotfix or a Service Pack? Will I be able to get source for that?
“We’ve built a system that allows us to publish any number of versions of source and symbols for a given product. We haven’t made any firm decisions on how often we’ll publish source and are open to customer feedback on those issues. For example, it’s clear that publishing source for each Service Pack makes sense, but it’s unclear if we’ll be able to do so for each Hotfix. Again, we’re looking forward to feedback here.
“In the meantime, also note that symbol files may no longer match a module if a framework DLL has been updated via a Hotfix. In those cases, the modules window will indicate that the symbols could not be downloaded for that module. Assuming a new symbol file was published, it can be downloaded and cached using “Load Symbols”.”