[Amrykid]

Its been almost a year since .NET 4 was released (12 April 2010, so about 11 months). Microsoft introduces a lot of new features but there maybe something you find is missing. Specify what you want to be included in 4.5 (or if they skip to 5.0).

What I would like are:

• A namespace for IMAPI (Image Mastering API) for burning cds.
  
• A namespace for Zip, etc.
  
• XNA included in .NET framework under a System.XNA namespace.

What do you want?

[nevergiveup]

I haven't covered all of .NET FRAMEWORK. Don't you think I need to know what the .NET FRAMEWORK has before I request a recommendation.

[eclipsed4utoo]

nevergiveup, on 04 April 2011 - 10:13 AM, said:

I haven't covered all of .NET FRAMEWORK. Don't you think I need to know what the .NET FRAMEWORK has before I request a recommendation.

Not necessarily. There are plenty of things that we know that the .Net framework doesn't do, or doesn't do efficiently.

[marinus]

Repair the System.Threading.Timers ,
there is some major problems there

[swehunter2000]

I would like better cross threading..

[Amrykid]

swehunter2000, on 04 April 2011 - 04:24 PM, said:

I would like better cross threading..

For WPF or Windows Forms?

[MATTtheSEAHAWK]

swehunter2000, on 04 April 2011 - 02:24 PM, said:

I would like better cross threading..

You took the words straight out of my mouth.
I hate the damn cross thcall read exceptions. I don't know if they can fix it but if they can fix it NOW.

Amrykid, on 04 April 2011 - 02:28 PM, said:

swehunter2000, on 04 April 2011 - 04:24 PM, said:

I would like better cross threading..

For WPF or Windows Forms?

I think WinForms. That is what I want.

This post has been edited by MATTtheSEAHAWK: 07 April 2011 - 04:58 PM

[Amrykid]

MATTtheSEAHAWK, on 07 April 2011 - 06:58 PM, said:

swehunter2000, on 04 April 2011 - 02:24 PM, said:

I would like better cross threading..

You took the words straight out of my mouth.
I hate the damn cross thcall read exceptions. I don't know if they can fix it but if they can fix it NOW.

Amrykid, on 04 April 2011 - 02:28 PM, said:

swehunter2000, on 04 April 2011 - 04:24 PM, said:

I would like better cross threading..

For WPF or Windows Forms?

I think WinForms. That is what I want.

Until then, you could always use Form.Invoke() and/or BackgroundWorker.

[swehunter2000]

Amrykid, on 07 April 2011 - 09:01 PM, said:

MATTtheSEAHAWK, on 07 April 2011 - 06:58 PM, said:

swehunter2000, on 04 April 2011 - 02:24 PM, said:

I would like better cross threading..

You took the words straight out of my mouth.
I hate the damn cross thcall read exceptions. I don't know if they can fix it but if they can fix it NOW.

Amrykid, on 04 April 2011 - 02:28 PM, said:

swehunter2000, on 04 April 2011 - 04:24 PM, said:

I would like better cross threading..

For WPF or Windows Forms?

I think WinForms. That is what I want.

Until then, you could always use Form.Invoke() and/or BackgroundWorker.

Yeah, the Win Form, and btw, that backround worker gives the same exeptions.. "could not call the control due to it was created in a other thread"

[AdamSpeight2008]

Then it not a problem with the framework, but a problem with how your his using it.

[MATTtheSEAHAWK]

Yea I tried making another thread and when that didn't work I tried to use background worker and that didn't work. It is a pain because I really need to do it sometimes.

[AdamSpeight2008]

Background Worker Tutorial. The most pertinent aspect is the section after the section For the more adventurous of you

[swehunter2000]

Yeah.. but im using it right.. but its sometimes the crossthread calls wont work for me..

[eclipsed4utoo]

MATTtheSEAHAWK, on 08 April 2011 - 04:50 PM, said:

Yea I tried making another thread and when that didn't work I tried to use background worker and that didn't work. It is a pain because I really need to do it sometimes.

It's relatively easy to interact with a UI control from a background thread, which is where most of the cross-thread exceptions occur.

[Core]

I'm just going to say this - try working with cross-thread operations in C++ and then we'll talk how hard it is to get them working in the context of .NET.