I've been doing Silverlight development for awhile now, and I was pretty sure that I had pretty good handle on figuring thing out. This one has me completely baffled however...
As you can see, the very property that Silverlight is reporting an error on, is directly where it should be! Any ideas? I've also found my Visual Studio being really slow, and I'm thinking a resinstall is in order. I just got a new laptop Lenovo W520, with a graphics accelerator. Not sure what is going on... any ideas would be appreciated!
Regards,
Richard
Let me guess: FinancialContracts is not actually a public property? It must be both public and a property.
Related
Not sure what is going on here, if it's just my computer, or a VS bug. It is annoying.
When scrolling, text in VS sometimes gets really messed up. it also happens to other window elements on occasion.
I've noticed something similar in Dreamweaver CS4 & CS5, so I don't know if it's my computer or something with WPF.
Any way to fix this problem?
Windows 7 Pro
This is most likely a general WPF issue, and could be related to your graphics drivers.
I would recommend looking for updated graphics drivers for your graphics card. If this doesn't work, try reducing the amount of hardware acceleration, as this tends to clean up many WPF rendering issues.
I would suspect this is a WPF issue that may be resolved by updating your graphics drivers if your card can handle it as Reed Copsey suggested.
If you don't have any luck with that, you can try turning off some of the hardware-accelerated rendering by going to the Tools menu, selecting Options then disabling the Automatically adjust visual experience based on client performance option and the following two options under the Environment > General section.
MSDN put up an article not too long ago that can help troubleshoot the problem.
http://msdn.microsoft.com/en-us/vstudio/ff716700
The first two things I would try would be to update your video drivers. Then maybe turn down hardware acceleration.
This KB article touches upon how to do it about half way down the resolution section.
http://support.microsoft.com/kb/263039
I have similar problems with my VS2010. It isn't a graphic driver issue but an issue with WPF/VS2010. I was hoping the SP1 would solve this problem, but it didn't.
Remember the Amiga boing demo? I was reading a 25th anniversary of the Amiga article and they mentioned it. Brought back some memories. I remember a WPF (called Avalon at the time) demo put together to mimic it. I did some googling and found it here. However, it seems to be extremely out-of-date as the XAML markup and the code-behind is rife with errors when I attempt to build in VS 2010 (re-targeted to CLR 4.0 Client Profile). Are there any WPF gurus out there who are able and willing to bring it into this decade? This would go a long way to understanding the WPF/XAML stack for me. Thanks!
Edit: I'm using the slightly updated version I just found here.
Edit the 2nd: I've gotten it to compile and show the nice gradient blue background, but not the bouncing checkered ball. The problem is that I cannot find the modern equivalent of:
<x:Include x:Content="{ball}" />
I have recreated this stuff for .NET 4.0. Solution is available by Boing link. Thanks for your suggestion. It was interesting!
Added
I have added solution code to codepaste.net. You can view it here.
What is the best way to do this? I want to get this working with nCover.
I made a run at this and came close... but in the end it didn't really work out for me.
The guy from Test Driven made a template for testing silverlight in nunit. I upgraded this to Silverlight 4.0 then I ran nCover.
The proof of concept worked great... but when I tried it on our actual product things fell apart pretty quick.
Many of our unit tests reference AGcore and others referent GUI objects, which is why I think I kept getting some sort of cross threading error.
I read that SilverUnit may be able to do this sort of thing... but you have to pay 700+ dollars per developer. I wish the guy who wrote that would consider selling it separately.
Oh well... someday maybe I'll see code coverage numbers... not today though :-)
zachary,
Can you provide more detail on "the proof of concept worked great"? NCover is not able to profile Silverlight because it does not support the CLR.
I know WF designer has re-hosting capability.
Since it's WPF-based, I thought it might be rehostable in web, using silverlight.
Does anyone have any experiece regarding this?
Or, does anyone know an easy and powerful web-based workflow designer solution for WF?
The WF designer can be hosted in the browser, just not with silverlight but as a wpfbrowser application. See details here
This requires the .net framework on the client.. but it does work.
When Microsoft introduce WF 4 at PDC2008, I specifically asked the question about rehosting in Silverlight and the answer was "No, it isn't something we are currently supporting but it seems there is some demand so we are conisdering it".
A little more than 2 years later and they aren't still supporting it so I guess it will be a while before we see that happening out of the box from MSFT
I'm working in the "WF area" too: the designer can't be rehosted in a web page. Keep in mind that WPF is quite different from Silverlight.
Not really answering you question, but... have a look at SnapFlow.
If you find something useful don't forget to write a short note here. ;-)
When working in VS2008 (C#) does VS2008 silently crash for anybody when working with WPF? If I touch the XAML it is most likely to crash. I can come back in, clean, then build, then run and it work until I have to touch the XAML again. Then start over again.
It is a solution with about 12 projects in it.
Thanks,
jeff
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=375594
Workaround:
Found real workaround at http://www.dotnet6.com/blogs/wesley_walraeve/archive/2008/10/22/visual-studio-2008-sp1-crashes-toolbox-gt-choose-items.aspx, which was removing TFS Power Commands 2008. Other people have had to remove other things.
SP1 solves a bit of the crashes, but indeed it crashes a lot. Especially when you mix and match winforms + WPF. The crashes alone were a reason to stick with winforms for a while for us ...
I found the problem to be with the AnkhSvn plug-in. I went to a nightlybuild and it is working good now. Anything above 2.0.6110.379.
I and some other people at my company have had a lot of problems when editing a resource dictionary and while a XAML window that uses that resource dictionary is open. Moral of the story, close all XAML windows if you're going to edit a resource dictionary.
We suffer the same problems... I noticed that resharper makes things worse for the WPF editor from time to time...
Ah well.. a daily VS crash keeps the doctor away ?
VS crashes at my computer very often: several times per day when I work with WPF. But usually it stops responding and I don't remember it to crash silently.
I know, it's not nice, but simply cleaning the solution works for me. At least until the next restart of VS, but until then you shouldn't get any crashes.