Comments for Reed Copsey, Jr.

Comment on Setting useLegacyV2RuntimeActivationPolicy At Runtime by Reed

Reed — Mon, 13 May 2013 18:13:18 +0000

Unfortunately, the runtime policy is either one way or the other, and once it’s set, it can’t be changed. Mixing mixed-mode and click once in a single process is going to be problematic unless you make sure things are built for the correct runtime (CLR 4).

Comment on Setting useLegacyV2RuntimeActivationPolicy At Runtime by Dangers of calling ICLRRuntimeInfo.BindAsLegacyV2Runtime at runtime | BlogoSfera

Mon, 13 May 2013 13:03:17 +0000

[...] http://reedcopsey.com/2011/09/15/setting-uselegacyv2runtimeactivationpolicy-at-runtime/ [...]

Comment on Setting useLegacyV2RuntimeActivationPolicy At Runtime by Mike

Mike — Fri, 10 May 2013 14:06:21 +0000

Thank you for your blog.

This works well for those apps. But I have a “portal” which contains mix mode apps and clickonce apps. So what happens is the user launches a mix mode app and then tries to load a clickonce app and the error message comes up

An error occurred while verifying the application. Error text: A runtime has already been bound for legacy activation policy use. (Exception from HRESULT:0×80131704

So is there a way to Unbind the legacy runtime. do you think calls to
void SetDefaultStartupFlags();
void GetDefaultStartupFlags();

would help, But I don’t know how to setup those methods with parameters or their .net calls

Thank you

Comment on Launching a WPF Window in a Separate Thread, Part 1 by Reed

Reed — Thu, 25 Apr 2013 16:06:26 +0000

Gennady,

Thank you for the updated info. When I wrote this article (in late 2011), the link and title was correct. A recent MSDN update for VS 2012 has broken it.

I’ve updated the article to link to the web browser sample, and noted that the original sample is no longer available.

-Reed

Comment on Launching a WPF Window in a Separate Thread, Part 1 by Gennady Vanin (Novosibirsk)

Gennady Vanin (Novosibirsk) — Thu, 25 Apr 2013 04:01:04 +0000

Hello, Reed,
your “Multiple Windows, Multiple Threads sample” link does not really point to used in article sample.

It points to MSDN “Threading Model” (.NET 4.5) which has the section with such title and respective snippets
This article has the only ref to one-window “Single-Threaded Application with Long-Running Calculation Sample” only.
So, I downloaded few times that one-window sample

Only if to switch the version of .NET 3.0 or 3.5 of this article, the section “Multiple Windows, Multiple Threads” has a reference to used by you sample.
Though, it is called “Multithreading Web Browser Sample” and has quite different link:
http://msdn.microsoft.com/en-us/library/ms771272%28v=vs.90%29.aspx

Probably it would have been better to give more correct/direct references and titles…

Comment on Using Behaviors to Allow the ViewModel to Manage View Lifetime in M-V-VM by Reed

Reed — Fri, 19 Apr 2013 15:31:38 +0000

Den,

I’ve written a bit about DI (with MEF) – you can click on the MEF category to see the articles.

I haven’t really tackled message services or messaging models. There’s a lot out there that already handles this, and once you understand the basics of MVVM, toolkits like MVVM Light, etc, should make a lot more sense. They handle those topics very nicely.

-Reed

Comment on Using Behaviors to Allow the ViewModel to Manage View Lifetime in M-V-VM by den

den — Fri, 19 Apr 2013 12:19:02 +0000

This is a great article. Brilliant!

Reed,
I am also interested if you have had discussed the following issue already?

Dependency Injection and a message service or messaging models?

Thanks,
den

Comment on Better User and Developer Experiences – From Windows Forms to WPF with MVVM: Conclusion by Reed

Reed — Mon, 15 Apr 2013 18:47:43 +0000

I see storyboards are a pure-View issue, which means there really is no reason not to use code behind for them. Attached properties or behaviors can often be used to trigger this if you want a xaml only solution, though.

Comment on Better User and Developer Experiences – From Windows Forms to WPF with MVVM: Conclusion by Gaurav

Gaurav — Sun, 14 Apr 2013 06:47:23 +0000

This is awesome, after reading this article I suddenly realized that working with MVVM is more fun then using WPF directly.
I have one question though – where should we initiate call to storyboards, code behind or View-Model or is there a way to do that in XAML?

Comment on Better User and Developer Experiences – From Windows Forms to WPF with MVVM: Conclusion by Reed

Reed — Mon, 25 Mar 2013 17:18:18 +0000

Glad that it helped! Thank you for the feedback.

Comment on Better User and Developer Experiences – From Windows Forms to WPF with MVVM: Conclusion by Jim

Jim — Mon, 25 Mar 2013 03:14:52 +0000

Awesome help – went from not getting any of the WPF magic to totally loving it.
Thanks!

Comment on Parallelism in .NET – Part 18, Task Continuations with Multiple Tasks by C# 5 Async, Part 2: Asynchrony Today : Reed Copsey, Jr.

C# 5 Async, Part 2: Asynchrony Today : Reed Copsey, Jr. — Fri, 22 Mar 2013 15:46:02 +0000

[...] via the use of Task Continuations. In addition, the Task class provides a new model for task composition and error and cancelation handling. This is a far superior option to the previous [...]

Comment on C# 5 Async, Part 3: Preparing Existing code For Await by Reed

Reed — Fri, 22 Mar 2013 15:43:25 +0000

When I wrote this, it was using the CTP – and was C# 4. I’ll adjust it now. Note that you can target .NET 4 using Microsoft.Bcl.Async (but it still requires the C# 5 compilers) available from http://nuget.org/packages/Microsoft.Bcl.Async/

Comment on MEF CompositionInitializer for WPF by How to use VS2010 solution included with "MEF CompositionInitializer for WPF" article? | BlogoSfera

Fri, 22 Mar 2013 05:00:29 +0000

[...] bumped into Reed Copsey, Jr.’s article “MEF CompositionInitializer for WPF”. I downloaded included there Composition.Initialization.Desktop.zip solution for Visual Studio 2010 [...]

Comment on C# 5 Async, Part 3: Preparing Existing code For Await by Модернизация Переоборудование Царз Минобороны

Модернизация Переоборудование Царз Минобороны — Fri, 22 Mar 2013 03:28:56 +0000

Hello Reed,
Why have you tagged your C# 5 articlles with “C# 4″ tag?

(I am interested to find and run code in C# 4 but not C# 5)

Comment on Performance and Optimization Isn’t Evil by Datacenter Acceleration - John W. Verity - Planning for Performance Is a Must

Datacenter Acceleration - John W. Verity - Planning for Performance Is a Must — Thu, 21 Mar 2013 20:07:39 +0000

[...] But I suspect it's more than that, which is why his article is still on the web and still enjoying enthusiastic referrals here and [...]

Comment on Long overdue Enum goodness in .NET 4 by Reed

Reed — Thu, 21 Mar 2013 17:24:37 +0000

Candide – It is slower, but that’s often not an issue. If you’re doing this in a tight loop where perf. matters, then yes, you might want to avoid this call. I do like the additional clarity involved in the method call, in most cases.

Comment on Long overdue Enum goodness in .NET 4 by Candide

Candide — Thu, 21 Mar 2013 17:01:17 +0000

enum.HasFlags is about a hundred times slower than testing the bit direcly.

Comment on Synchronizing .NET 4 Tasks with the UI Thread by Reed

Reed — Thu, 14 Mar 2013 15:55:33 +0000

Yes – You typically need to specify TaskScheduler.Default on the continuation if you explicitly want it to not run on the previous thread.

Comment on Synchronizing .NET 4 Tasks with the UI Thread by Philipp

Philipp — Thu, 14 Mar 2013 09:16:49 +0000

One potential gotcha here is that if you schedule a continuation for such a task, at least in .NET 4, it will continue to use that TaskScheduler. So there is a risk of invoking follow-up work on the UI thread. I find that most developers aren’t aware of this.

Comment on WPF – Common Dependency Property Exception by Http://Yahoo.Com

Http://Yahoo.Com — Thu, 28 Feb 2013 21:54:57 +0000

This posting, Window Covers “WPF – Common Dependency Property Exception : Reed Copsey, Jr.
” ended up being remarkable. I am creating out a
reproduce to demonstrate to my associates.
Many thanks,Joanna

Comment on Better User and Developer Experiences – From Windows Forms to WPF with MVVM: Conclusion by Tomas

Tomas — Sun, 24 Feb 2013 09:57:24 +0000

Thank you for these superb articles. I am VB developer and I was frightened with WPF. There are so many options how to achieve the same thing. I didn’t know where to start. Now I have really understood WPF with MVVM pattern.

Comment on ConcurrentDictionary used with Lazy by QuanEdys

QuanEdys — Tue, 12 Feb 2013 02:40:09 +0000

Great idea, makes a lot of sense as well

Thank you for the post.

Comment on Better User and Developer Experiences – From Windows Forms to WPF with MVVM: Part 4, Data Binding by Brandy

Brandy — Tue, 22 Jan 2013 10:04:55 +0000

It’s good to get a fresh way of looknig at it.

Comment on Setting useLegacyV2RuntimeActivationPolicy At Runtime by Reed

Reed — Fri, 11 Jan 2013 18:49:51 +0000

I’ve never tried it. The trick would be making sure your code ran early enough that it didn’t fail. It might be possible, but it needs to be one of the first things executed to work properly…