Does anyone have any success with WinForms ChartFX 6.2 on Vista or Windows? I'm after a sanity check that it's not just our code. If it's a known issue I can say that upgrading is the only solution.
Currently we get an exception in the Scatter Chart when adding annotations, it looks like it's in the GDI, but the exception can't be caught or handled and is slightly intermittent.
SoftwareFX forums have said that it should work.
Related
I have one very old application with millions loc developed using .NET FX 3.5.
The winforms embedded IE 11. But since MS is going to retire IE 11 soon. May I know is there any other browser which I can still embed into my WinForm?
I have no luck with WebView2. Doesn't seems to work.
The reason why WebView2 does not work is related to your current environment. WebView2 requires .net Framework 4.6.2 or later.
For more detailed, you could refer to this document.
Regarding the IE 11 you mentioned, how do you embed it? Do you use the WebBrowser control or something else?
According to this official blog, IE engine MSHTML (Trident) will continue to be supported, so I think you don’t have to worry about it.
I have a user interface which is targeted to use .Net 3.5. In this user interface there are some graphical issues (sliders have a stair-step effect, some text is skewed) and this is caused (so I've been told) by my new graphics card assuming .Net 4.0 is installed. This calls some function which has (since 3.5) been altered/improved, however in the 3.5 it behaves differently than the graphics card assumes, and therefore renders the responses incorrectly.
In an attempt to fix this issue I decided to upgrade my project to utilize .Net 4.5 due to several large WPF improvements.
Upon installing .Net 4.5 on my system, however, I immediately saw my graphical issues disappear, BEFORE I changed my project to target .Net 4.5.
Does anyone know what is going on? This is a very troubling side effect that was completely unanticipated; my project says it's utilizing 3.5, but it's rendering as if it's using 4.5.
.Net 4.5 is not side-by-side with .Net 4.0 .
It will actually replace 4.0.
On channel 9 I have listened to an interview from the BCL team where they promise that it would do so
without any side effects (or at least no bad side effects)
But for WPF there obviously is some Changes.
In Your case it is for the better - at least when somebody is installing .Net 4.5 it will be better.
I have a case where it is good in .Net 4 and looks bad in .Net 4.5 - so I hope my clients don't update
before I find a solution ...
But I understand that Your problem for the moment has more priority ...
Below link to: .NET 4.5: BCL Team - Improvements and Evolution
http://channel9.msdn.com/posts/NET-45-Conversation-with-the-BCL-Team-Improvements-Evolution-and-More
We're in the process of creating a Silverlight project and wondered how we could validate/test if it would run on Moonlight. From regular .Net to Mono there is the Mono Migration Analyzer which generates a report on which methods are missing in Mono to provide full support.
Are there any similar tools from Silverlight to Moonlight?
As I know there aren't any and event wouldn't be by my opinion.
The situation with moonlight is little bit more complicated.
With mono you're checking just clr methods towards standard. That's pretty easy.
Moonlight 1.0 is only stable version and should be 100% compatible with Silverlight, XAML is covered, but there are of course some bugs, the only comparision is on this page: http://go-mono.com/moonlight/MoonlightStatus.aspx.
Moonlight 2.0 is in beta state, there is clr part that can be checked with moma towards the mono version it's based on, cause the binaries are only stripped by mono linker. The API will be quite near 100% if not fully compleated. The rest is same like with Moonlight 1.0.
The status page is here: http://go-mono.com/moonlight/MoonlightStatus.aspx?v=2
Like Yakeen said, 2.0 is in beta. The best way to test is going to be installing moonlight on a test box and manually testing your site.
If it were me, I'd create a Virtual Machine with some flavor of Linux+Firefox and install the beta from their download site
I have an application, which I develop in VS 2008 and I target .NET 3.
Unfortunately when I install on a clean computer with .NET 3, it crashes. And besides the usual TypeInitilisationError, I have no clue why.
Updating the same machine to .NET 3.5SP1 makes it run fine.
Is there something broken in VS2008 that prevents from telling me a more detailed error?
How can I be sure I don't use any of the newest classes of the framework?
It is true that I found myself using DropShadowEffect which belongs to 3SP1. I removed it.
But still...it does not work.
What am I doing wrong?
Have you tried to determine which version of the framework is installed on each computer. If you're using .Net 3.5 SP1 to compile the program it actually includes .Net 3.0 sp2 which has some extra features (MultiSelector class to name one) which are not available in .Net 3.0 sp1 which is the default install with .Net 3.0 download from Microsoft.
You can try here for some software that will help:
NetVersionCheck
EDIT:
Visual Studio won't tell you about any errors for this because everything seems fine with the version of .Net 3.0 that it's using. I ran into this problem using the WPF toolkit as it requires the MultiSelector class which didn't arrive until .Net 3.0 sp2. So, Jonathan, if you can show us the error output from your program on the 'Fresh' .Net 3.0 computer then we could probably tell you what you're using that is in .Net 3.0 sp2 that isn't supported in lower versions.
Also, I usually use VS2005 with programs that I want to run under a lower runtime than .Net 3.5sp1, but this really only applies to .Net 2.0 apps.
If we knew what components from .Net 3.0 that you're using, it would help as well!
Noah
Thanks for the answer.
Because of VS2008, on my dev computer i have the latest 3.5SP1.
But in Visual Studio i selected 3 as a target.
And to check i install on a clean computer with 3.0...
So your proposition do tells me which framework is installed, but does not tell me what in my program uses in the newest framework that is not present in 3.0.
Moreover, something must be broken in VS2008 as it should warm me for that...
I feel like this is a problem with VS 2008, but obviously MS feels differently.
VS 2008 comes with .NET 3.5, some .NET 3.0 service pack, and .NET 2.0 SP1. It can only detect whether you are using things that don't belong to a version that is installed on your machine, not whether you are conforming to some service pack. This means that if you target .NET 2.0, but install your software on a machine that does not have .NET 2.0 SP1, if you use anything specific to SP1 your application will fail when it tries to make the call.
The only way to detect this that I have seen is to inspect the changelist of the service packs or to target .NET 3.5. If .NET 3.5 is installed, so are the service packs that come with it. It's not a good solution, but it's the only one I've found.
I made a WPF app that uses Web Services. It is failing on all computers except the dev machine with the message -- System.MissingMethodException. I guess the point where it fails is the point where it tried to access the Remote webservice (website).
Has anyone had any experience with WPF and webservices? Should I spend 2 more days porting it to .Net Winforms, or should I keep trying to make it run?
The problem is, in Vista all I see is 'This application has experienced an error and will shut down' and in XP I just a system error dialog and I can't point out where the error is.
My guess is that there is some DLL which is on my PC and not on other people's PC which has the missing method causing the error.
I made this using .Net 3.5.
Any ideas?
Indeed, you have identified the most probable cause of your problem: a mismatch between the installed libraries on your dev machine and the prod machines.
You can use the fuslogvw.exe to enable Fusion to log binding errors.
Also check whether you have installed the same (versions of) .NET framework everywhere (SP1?)
Did you use SP1? Is SP1 installed on the target machine?
Getting a full stack trace would allow you to diagnose this further.