next »

[radio42]

As the .Net Framework is evolving and the .Net 4.0 version is now available and installed on almost any machine these days, I am planning to use the v4.0 .Net Framework for the next BASS.NET release - which means the v2.0 or v3.5 Frameworks will not be supported anymore in the future.
This also means, that your applications (using Bass.Net) might also need to be 'migrated' to the new v4.0 .Net Framework.
This shouldn't be any real effort, as the v4.0 version is almost 100% compatible with the v2.0 or v3.5 Framework.

However, I'll give you a choice here...
...please select the .Net Target Framework the next BASS.NET version should be based on.

...and if there are any serious reasons (except the 'I don't want to rebuild my app because I am lazy') to not upgrade to the v4.0 .Net Framework, please post them here.

THX
Bernd

[muntablues]

Hi Bernd

I use .NET 2.0 at the moment. And its just because XP SP3 has .NET 2.0 included but not 4.0. So I think not all XP users have 4.0 installed.

But if you want to switch, I will not have a problem at all.

BTW why do you want to switch to 4.0. Are you really doing jobs which make 4.0 necessary? Or is it just to support 4.0 at all?

MB

[radio42]

It's the same thing as when switched from .Net v1.0/1.1 to v2.0/3.5.
Time goes on and the .Net v2.0/3.5 Framework is about to 'expire'.
New features are based on the v4.0 .Net Framework only an it has a whole new security concept (transparency, security level2, etc.).
And several people are wanting to have a pure v4.0 .Net Framework based lib....that's all.
E.g. if you have a clean Win7 system with only the .Net v4 framework one it and are using VS2010...then all defaults to v4.0.
Some other reasons are, that the .Net v4 Framework supports things like:
- background garbage collection
- better multi-core support
- etc.

[nr1]

.Net Framework v4 => go for it

Any new features planned, or is it just porting to .net 4?

[bensam56]

kindly also make 3.5 framework version.

[radio42]

Guess I am going to build it for both versions (.Net v2.0 and v4.0)...
...no new features planned so far.

[jjohnston]

Would love a .NET 4.0 version! :-)

[big_gun]

Radio42:

While I love the fact you are targeting .net 4.0 I think you should also target 2.0 since 2.0=3.0=3.5. and 4.0=4.0.

Rick

[radio42]

Here is a pre-version of the forth-comming Bass.Net v2.4.8.1:

    www.un4seen.com/filez/4/Bass24.Net_pre.zip

Note:
This build already contains four Bass.Net assembly versions (each in a seperate sub-folder):
.\v2.0    : Bass.Net for .Net 2.0
.\v4.0    : Bass.Net for .Net 4.0
.\compact : Bass.Net CE for .Net CompactFramework 3.5
.\iphone  : Bass.Net iPhone for .Net CompactFramework 3.5

The final version will contain the exact same assemblies but contain a re-worked help system.

Note: There is no need to supply a dedicated version for .Net 3.5, as it is still based on the .Net 2.0 version and just contains various additions.
AS such you can always use the .Net 2.0 Bass.Net version with the .Net 3.5 framework!

[floele]

Just to add an opinion: A v4.0 variant is fine, but please keep version 2.0 active for a while longer.
With Windows 7 .NET 2.0 is finally available on most computers, if I had to switch to version 4.0 with my app now, this advantage would be gone again, because 4.0 is not installed on Windows 7 by default. Also 4.0 is no longer compatible with Windows 2000. So I do not plan to move to .NET 4.0 any time soon with my app - not for reasons of lazyness, but to increase the probability of a usable .NET version being available on the target computer. The 2.0 version of my app can run on Framework 2.0 and 4.0, but a 4.0 version could only run the computers that have the very latest version of .NET installed. And from a user's perspective, there is no advantage by using .NET 4.0.

the .Net 4.0 version is now available and installed on almost any machine these days

Where do you get this information from? I am pretty sure this is not the case.

[radio42]

There are a couple of advantages by using the .Net v4.0 version (e.g. dynamic background GC) - but however...
as you can see above...that is actually the plan...that's why a v2.0 AND v4.0 .Net version are shipped with Bass.Net!

[muntablues]

There are a couple of advantages by using the .Net v4.0 version (e.g. dynamic background GC)

Do you want to say, that MixedMode assemblies (e.g. for Asio) are not needed anymore?

[radio42]

No, I don't want to say that.
I just wanted to say, that there are a couple of improvements in the .Net v4 framework in general.

[floele]

Sure, there are improvements, but nothing that "sells" (as far as I know).
From a user's perspective, I would not have any good reason to require .NET 4.0.

[radio42]

That's up to everyone's own decission...that's why I decided to deliver both: a v2.0 and v4.0 .Net version.

[floele]

It's good that you did and I wanted to confirm your good decision