Peter Ritchie's MVP Blog - All Comments

re: Performance Implications of try/catch/finally

PeterRitchie — Fri, 03 Oct 2008 14:05:14 GMT

@Norman. Yes, due to various guarantees it has to disable *some* optimizations in the try block.

For example:

try

{

i = 1;

i = 2;

methodThatMightThrow();

i = 3;

Trace.WriteLine(i);

}

catch(Exception)

{

}

Trace.WriteLine(i);

The compiler/runtime guarantees that the state of i will be 2 when the exception is thrown (and that i will be 1 if an exception occurs before setting it to 2--remember there are asynchronous exceptions). Normal optimizations would think that i only ever really needs to be 3 and would optimize as such.

re: Performance Implications of try/catch/finally

Norman Diamond — Fri, 03 Oct 2008 04:45:39 GMT

Theoretically the try part of this try statement doesn't have to disable optimization, but the finally part has to disable (to some extent) optimization of the try part. The reason is that the finally part fetches the value of count.

As an analogy, suppose you compare two programs, one with trivial uses of count the way your first program did, and the other one with a for loop and a call to some function with count as an argument in that function call. Would you say that the for loop causes the decrease in optimization, or would you say that passing count as an argument causes the decrease in optimization?

re: Thread.Abort is a Sign of a Poorly Designed Program

PeterRitchie — Fri, 26 Sep 2008 14:07:08 GMT

@Rajeev. Second last paragraph, when I link to another post that describes how to cooperatively terminate a thread. The only way to reliable terminate a thread is to get it to do it itself.

re: Thread.Abort is a Sign of a Poorly Designed Program

Rajeev — Fri, 26 Sep 2008 09:11:45 GMT

what in your opinion is the optimal way of terminating a thread then?

re: Sudden "...you must have Terminal Server User Access permissions on this computer." Error.

Vijay — Sun, 21 Sep 2008 06:38:57 GMT

Working fine.....Thanx a lot...

re: Sudden "...you must have Terminal Server User Access permissions on this computer." Error.

Jay — Sun, 21 Sep 2008 06:09:36 GMT

Thanks.. this works like a charm.

re: Software Process and Reduction of Quality

Thomas — Fri, 19 Sep 2008 02:45:48 GMT

I remember when innovation and cool products were more important than the bottom line at MS.

Not the case anymore. Products like Zune are perfect examples of what happens when a company starts thinking about money and not what people want.

It’s all about $ and politics these days at MS.

I’m a 15 year dev and yes I work in the .NET framework now but honestly I am starting to work in other platforms because MS has lost touch.

You cannot outsource innovation. It comes from individuals. Yes these individuals need to have deadlines but they are unacceptable at MS therefore innovation has come to a HALT.

Please, release yet another version of MS mobile while I check my mail on my iPhone.

re: Sudden "...you must have Terminal Server User Access permissions on this computer." Error.

Bill C — Thu, 18 Sep 2008 18:33:48 GMT

not to confuse the issue but we have 3 of us using mstsc with the same administrator login to many 2003 servers and I am the only one to get that error. I have XP SP2, one co-worker has XP SP3, and another has Vista. They do not have any issues. I use the /console option and they use the /admin option (SP3 and Vista change)

I tried upgrading to SP3 but got a BSoD that I spent 2 days trying to recover from.

Anybody have any ideas?

For Citrix USERS

Gary — Wed, 17 Sep 2008 17:39:36 GMT

support.citrix.com/.../CTX103922

Is how I had to fix this, hope it helps.

re: Sudden "...you must have Terminal Server User Access permissions on this computer." Error.

Julio — Tue, 16 Sep 2008 20:41:02 GMT

tengo un problema cuando me conecto al terminal server me sale el siguientes mensajes:

To log on to this remote computer, you must have terminal server user Access permissions on this computer. By default of the remote desktop users group have these permissions. If you are not a member of the remote desktop users group or another group that has these permissions, or if the remote desktop user group do not have these permissions, you must be granted these permissions manually.

re: My Visual Studio 2008 Code Analysis Rules

PeterRitchie — Wed, 10 Sep 2008 18:23:27 GMT

@Paulo I've run the rules without problem in both the RTM version of 2008 (9.0.21022.8 RTM) and the SP1 version of 2008. (9.0.30729.1 SP).

If you've installed a Beta, I recommend uninstalling it before upgrading to a non-beta version. Sometimes this means completely uninstalling all Visual Studio versions to get it to work proberly.

Visual Studio betas are not kind to your machine.

re: 'System.Threading.Thread.Suspend()' is obsolete: 'Thread.Suspend has been deprecated...

Ali Zamurad — Wed, 10 Sep 2008 17:47:03 GMT

First off - Great work Peter. I am wondering if you could suggest some in my situation. I have a GUI app which needs to be very responsive and it depends upon the data that come in files, so I created a background thread that runs infinitely and pooling files that got parse and displayed on the GUI. Since the GUI is dynamic and can change what file should be pooled now I want to suspend and resume that backgroud thread - this is where I think I could use your class. In the mean time I tried to use Thread.Abort but sometimes it does not finishes the thread. Also even I shutdown the main GUI the thread since dangles and appear in the Task Manager. The thread property Isbackground is set to true. What am I missing?

re: Becoming a Visual Studio Jedi Part 1

Turkey — Wed, 10 Sep 2008 17:14:01 GMT

Thanks You , Perfect Docs

re: Becoming a Visual Studio Jedi Part 1

Dave — Wed, 10 Sep 2008 03:29:03 GMT

Use at least a 24" monitor - Two of them is better.

Dew Drop - September 9, 2008 | Alvin Ashcraft's Morning Dew

Dew Drop - September 9, 2008 | Alvin Ashcraft's Morning Dew — Tue, 09 Sep 2008 12:43:00 GMT

Pingback from Dew Drop - September 9, 2008 | Alvin Ashcraft's Morning Dew

re: Becoming a Visual Studio Jedi Part 1

dadsit — Tue, 09 Sep 2008 01:11:56 GMT

disable all the toolbars. they are a waste of space. customize the menus by adding the solution configurations (debug/release) and maybe the solution platforms to the build menu. You need to change those, what, once or twice a day?

and if you can't use Resharper, then you are working in the wrong environment. visual studio is a good starting point, but without the added power of Resharper, it is distinctly lacking...

re: My Visual Studio 2008 Code Analysis Rules

Paulo — Mon, 08 Sep 2008 23:18:02 GMT

Loading this in the a non-Beta 2008 (9.0.21022.8 RTM) gives me an error:

Error 208 CA0053 : Unable to load rule assembly 'C:\Program Files\Microsoft Visual Studio 9.0\Team Tools\Static Analysis Tools\FxCop\Rules\PRI.CodeAnalysis.Rules.Design.dll': Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.

Is this something in my configuration, or did something change from the Beta that broke these rules?

I'm chasing a debugger crash issue that I think may be related to a recursive property, so this rule of yours would be extremely helpful!

For completeness, here's what I have loaded:

Microsoft Visual Studio 2008

Version 9.0.21022.8 RTM

Microsoft .NET Framework

Version 3.5

Installed Edition: Enterprise

Microsoft Visual Basic 2008 91899-153-0000007-60707

Microsoft Visual Basic 2008

Microsoft Visual C# 2008 91899-153-0000007-60707

Microsoft Visual C# 2008

Microsoft Visual C++ 2008 91899-153-0000007-60707

Microsoft Visual C++ 2008

Microsoft Visual Studio 2008 Team Explorer 91899-153-0000007-60707

Microsoft Visual Studio 2008 Team Explorer

Version 9.0.21022.8

Microsoft Visual Studio 2008 Tools for Office 91899-153-0000007-60707

Microsoft Visual Studio 2008 Tools for Office

Microsoft Visual Studio Team System 2008 Architecture Edition 91899-153-0000007-60707

Microsoft Visual Studio Team System 2008 Architecture Edition

Microsoft Visual Studio Team System 2008 Database Edition 91899-153-0000007-60707

Microsoft Visual Studio Team System 2008 Database Edition

Microsoft Visual Studio Team System 2008 Development Edition 91899-153-0000007-60707

Microsoft Visual Studio Team System 2008 Development Edition

The American Heritage® Dictionary of the English Language, Third Edition Copyright © 1992 Houghton Mifflin Company. Electronic version licensed from Lernout & Hauspie Speech Products N.V. All rights reserved.

Microsoft Visual Studio Team System 2008 Test Edition 91899-153-0000007-60707

Microsoft Visual Studio Team System 2008 Test Edition

Microsoft Visual Web Developer 2008 91899-153-0000007-60707

Microsoft Visual Web Developer 2008

Crystal Reports AAJ60-G0MSA4K-68000CF

Crystal Reports Basic for Visual Studio 2008

Thanks!

re: Becoming a Visual Studio Jedi Part 1

charris — Mon, 08 Sep 2008 14:47:48 GMT

Additionally, turn off your shell animations too. Sliding effect is so awesome, but not practical.

re: Software Process and Reduction of Quality

PeterRitchie — Fri, 05 Sep 2008 15:15:48 GMT

@Dan. Sure, the majority of them may not provide comment; but by not being involved with the community an organization is cutting off a huge potential feedback avenue.

If an organization has found they aren't getting any feedback through community involvement, they've either written a perfect API/SDK or simply aren't involved in a way that fosters communications (e.g. they reject suggestions, provide a means of logging feedback but make it high-friction, etc.).

re: Software Process and Reduction of Quality

Dan Blair — Fri, 05 Sep 2008 15:08:26 GMT

>In the case of producing an API or and SDK, I believe these practices includes community involvement.

I agree with your comment, but I have come to find that most developers (consumers of your API or SDK) just don't care enough to provide comment. They are too busy doing whatever it is they aren't doing well. If you have a significantly large population of users that you can find people with passion then you are fortunate, take care of them and rmember them for the future.