Welcome to MSFN

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


Sign in to follow this  
Followers 0
eatup

My .NET 3.5 graphics app is 8x slower in 7/8 than XP!

5 posts in this topic

What can I do?  Targetting the app for .NET 4.5 didn't do nothing for it.  By slow, I mean the refresh cycle to display stuff in the app lags like hell in 7/8...  Why would the same source code produce sucky results in 7/8 than XP.  Was the .NET runtime in 7/8 that poorly coded?

 

An analogy is:  If my app was a game, the fps in XP would be something like 48, in 7/8 something like 8!

Edited by eatup
0

Share this post


Link to post
Share on other sites

Do consider recompiling it with VC# 2005 instead (if at all possible), because that would reduce the .NET framework version required to 2.0, making it much lighter. The Visual C# 2005 Express Edition ISO continues to be available for free from MS, although they don't advertise it. If .NET is to blame, then we're speaking of a situation where lighting the application should make a big difference, and when thinking about lighting a .NET application, VC# 2005 is perhaps the best option in what regards the funcionality to overall size ratio. Than again, if this experiment results in no perceptible difference, then the problem must lie elsewhere.

0

Share this post


Link to post
Share on other sites

^ is it possible to just target .NET 2.0 from VS2012?  I doubt VS2005 would load the source code created with VS2012...

0

Share this post


Link to post
Share on other sites

you can target .net 2.0 with VS2012, but it is very old. What is your application doing?

0

Share this post


Link to post
Share on other sites

My suggestion is "do create a version targetting .NET 2.0" just for test purposes, not for release or any real-world use.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.