User profile for Bart Read

Dear RichardD, Thank you for your delicious remarks. Iâ€™ve had them mounted on the wall behind me along with the others. I like to read them in the morning before quaffing a chalice of fresh sacrificial blood and indulging in a spot of maniacal laughter. I find that sets me up for a day of rapacious empire-building quite wonderfully. Diabolically yours, =========================== Bart Read Denizen of Darkness Red Gate Software Ltd / comments

Dear RichardD, Thank you for your delicious remarks. Iâ€™ve had them mounted on the wall behind me along with the others. I like to read them in the morning before quaffing a chalice of fresh sacri...

0 votes

I'm sorry you're having problems downloading .NET Reflector. I'm not sure why you should be because, as far as I can tell, the site is up and working fine. I've tried from both Firefox 3.5.9 and IE8 and everything seems OK, regardless of whether I check the checkbox or not. Once you click "Download" do you not find yourself on a page which says "Your download of .NET Reflector will start shortly. If it does not start, please click here."? This page also includes brief how to instructions for using .NET Reflector Pro. After you've filled out the text fields, and hit "Download" you should find that these controls disappear from the page (it's actually replaced by a completely different page). As an aside, if you update from within .NET Reflector itself you should find yourself directed to a version of the page that does not include the registration/newsletter sign-up step: you can just click "Download", and the file should come straight now. The only thing I can think is that your browser might be blocking download of the file. For example, in IE you might see a message like, "To help protect your security, Internet Explorer blocked this site from downloading files to your computer. Click here for further options...," just below the toolbar and tabs. It might also be worth, in Firefox, going to Tools > Downloads to make sure that the browser hasn't silently downloaded the file in the background. It's possible to stop the Downloads window popping up when you download files so, if that's the case, you may find you have several copies of the zip file on your machine. If none of this works, please get back to me. Thanks, Bart / comments

I'm sorry you're having problems downloading .NET Reflector. I'm not sure why you should be because, as far as I can tell, the site is up and working fine. I've tried from both Firefox 3.5.9 and IE...

0 votes

jrista wrote: I know you have said that it would always remain free, however given the trend (progressive commercialization and forced downloads via the web site for bogus reasons such as "people might become confused", which are really just a way to push Reflector Pro on us for $200) I can certainly understand your frustration but, to be absolutely clear, there's nothing bogus about this at all. Alex is right: our lawyers advised us that we would need to give everyone the opportunity to view the licenses for .NET Reflector and .NET Reflector Pro when upgrading from v5 to v6. Doing this makes it clear to anyone downloading the tool that it now includes a piece of commercial software with a 14-day trial period, and not just a free tool. Quite a few organisations would potentially have problems with this if we didn't do it, and unfortunately it's not enough to simply include the license agreements in the zip file (which we also do). We could have done this by popping up a dialog box as soon as you start .NET Reflector, but that didn't seem particularly friendly. Doing things the way we have - disabling automatic updates and redirecting to the website on the server side - means that we only have to show people who are upgrading from v5.x to v6.x the license agreement once. Automatic updates will work again from v6.1 onwards (you won't need to go to the web page so you can view the license agreements again). The reason you still get the web redirect from v6.0 to v6.1 is that we had to be sure anyone upgrading from a v6.0 early access build would be given the opportunity to view the license agreements. I hope that clears things up a little. Thanks, Bart / comments

jrista wrote: I know you have said that it would always remain free, however given the trend (progressive commercialization and forced downloads via the web site for bogus reasons such as "peopl...

0 votes

Hi again, You should find that this bug is fixed in the .NET Reflector 6.1 release. Please see this post for more information: http://www.red-gate.com/MessageBoard/viewtopic.php?t=10577 Hope that helps. Thanks, Bart / comments

Hi again, You should find that this bug is fixed in the .NET Reflector 6.1 release. Please see this post for more information:http://www.red-gate.com/MessageBoard/viewtopic.php?t=10577 Hope that he...

0 votes

Hi there, I'm afraid that, due to .NET Reflector's popularity, we don't distribute older versions because we are unable to support them. As Clive suggests, your best bet is to try to contact the author of the add-in. Contact details are available on this page: http://www.sandpapersoftware.com/Main/Reflector.html It is odd that it opens the Red Gate site in that case though, so we'll try to figure out why and will aim to get a fix in the next release of .NET Reflector. We're adding support for the C# 4.0 and VB 10 language extensions in .NET 4 at the moment, so we'd hope to have something out in April or possibly May. Thanks, Bart / comments

Hi there, I'm afraid that, due to .NET Reflector's popularity, we don't distribute older versions because we are unable to support them. As Clive suggests, your best bet is to try to contact the au...

0 votes

Hi there, Thanks for the enquiry. We'll make full pricing information available when the product is released, but for now I can tell you that a single user license of .NET Reflector Pro will initially cost $195, with discounts being available for multi-user licenses, following a similar pattern to our other products. .NET Reflector Pro will also be added to the .NET Developer Tools bundle, so anyone who has purchased the bundle with support and upgrades, and is still within the S&U period, will get .NET Reflector Pro at no additional cost. The standard version of .NET Reflector 6, which includes a number of bugs fixes and improvements over the current 5.1.x release, will remain free. Thanks, / comments

Hi there, Thanks for the enquiry. We'll make full pricing information available when the product is released, but for now I can tell you that a single user license of .NET Reflector Pro will initia...

0 votes

No problem. You're very welcome! / comments

No problem. You're very welcome!

0 votes

Hi there, Thanks for your comments about Mono support. I can confirm that support for running Reflector under Mono will be officially dropped with the release of version 7. We'd planned to make an announcement about this shortly but, since you've asked, I'm happy to provide some more detail about why this is. Incidentally, although I didn't make direct mention of it in my EA announcement I did allude to this when I described how v7 needs .NET 3.5 or later to run: http://www.simple-talk.com/community/bl ... 96204.aspx Obviously this news will come as a disappointment to some, but we made the decision for a couple of reasons. Firstly, we want to keep Reflector current in terms of support for newer technologies. This may still have been possible whilst continuing to limit ourselves to .NET 1.x compatibility, but would have become increasingly difficult and would ultimately limit our ability to develop the tool in the way we'd like. Whilst Mono supports many of the technologies in later framework versions, a crucial missing link is WPF, which would have a big impact on what we could do with the UI, and also what we might be able to do to provide specific support for technologies such as Silverlight. Certainly there are things we can do without this but, as I've said, it will become increasingly difficult for us to take the tool forward as we'd like with our hands tied technologically. This leads me onto the second reason... It's possible none of the above would matter if Mono were in relatively widespread use throughout the Reflector community, but the final nail in the coffin was the realisation that amongst Reflector users Mono is less commonly installed (never mind used) than .NET 1.x, and we'd already taken the decision to stop supporting the latter. Due to this very low penetration amongst Reflector users I could justify neither the extra effort required to support Mono, nor the restrictions supporting it would place on future development. Note that I'm not making any comment on the overall adoption of Mono, just its prevalence in the Reflector userbase. Obviously any assemblies compiled with Mono (or .NET 1.x, for that matter) should continue to open fine in Reflector. If Mono implemented WPF we might take another look at it, although there are some stability issues running on Mono, which I mentioned in an earlier post, that I think we'd need to take a look at before I'd be happy to claim official support. I hope that clarifies matters for you and, once again, thanks for posting your feedback. Kind regards, Bart / comments

Hi there, Thanks for your comments about Mono support. I can confirm that support for running Reflector under Mono will be officially dropped with the release of version 7. We'd planned to make an ...

0 votes

Hi cipher, No problem. I note that even previous versions don't work perfectly with Mono: it's relatively common for .NET Reflector to simply exit, though this might be due to the "Show PDB symbols" setting. Please see this post from Miguel for more information: http://weblogs.asp.net/nunitaddin/archi ... 1-2-3.aspx If you're having problems with the current 5.1.6.0 build, this might be why. The next Mono compatible build will be 5.1.7.0, and will only work on Mono, but will be identical to 5.1.6.0 in all other ways. We'll release it at the same time as .NET Reflector 6. Thanks, Bart / comments

Hi cipher, No problem. I note that even previous versions don't work perfectly with Mono: it's relatively common for .NET Reflector to simply exit, though this might be due to the "Show PDB symbols...

0 votes

I tracked this down and fixed it this morning. It'll be available in the next release of .NET Reflector. Actually what I did was simply to revert the change since having to hit F to activate the file menu after pressing ALT seems a lot less problematic than us breaking ALT-TAB behaviour - a safe fix for the menu focus issue is going to take a bit of investigation so it's unlikely to make it into the next release because we have other priorities. HTH. Thanks, Bart / comments

I tracked this down and fixed it this morning. It'll be available in the next release of .NET Reflector. Actually what I did was simply to revert the change since having to hit F to activate the fi...

0 votes

How can we help you today?

Bart Read

Comments