Move to .net 4.5

[SimonCropp]

The reasons for doing this are as follows

• Allows some better optimization in the core via the use of new APIs provided in 4.5
• Some of our Satellite dependencies are already moving 4.5. For example Unity
• 4.5 was release in mid 2012 so it has been out for reasonable amount of time
• Less testing surface area
• Also allows us to take advantages of the other various improvements in 4.5 http://msdn.microsoft.com/en-us/library/ms171868(v=vs.110).aspx#core

What this means for consumers

• The new minimum Visual Studio version will be Visual Studio 2012
• The new minimum server OS will be 2008
• The new minimum desktop OS will be Vista SP2
• All assemblies (and nugets) that depend on the core will be upgraded to 4.5

Note the earlier versions of NServiceBus will still be compatible and supported for .net 4

For more information on .net 4.5 see

• .NET Framework 4.5 – Core New Features and Improvements http://msdn.microsoft.com/en-us/library/ms171868(v=vs.110).aspx#core
• .NET Framework System Requirements http://msdn.microsoft.com/en-us/library/8z6watww%28v=vs.110%29.aspx

[andreasohlund]

@udidahan do you see any issues with moving to .net45?

[udidahan]

After taking everything into account, I think that we can make this move.

[andreasohlund]

Excellent, lets include this in 5.0.0

[chrisbednarski]

Ouch. Win 2003 Server extended support finishes July 2015.
How far away is v5? (12 months+)

[johnsimons]

@chrisbednarski are u guys still on win 2003?

[chrisbednarski]

@johnsimons lots of our clients definitely are. I need to find out when our company drops support for it.

[johnsimons]

@chrisbednarski
That just means that your clients can only upgrade to v5 when they upgrade OS.
NServiceBus v4 will remain clr v4

[chrisbednarski]

Since we're an ISV & write software for our clients (deploy NSB on their servers), it forces us to stay on v4. Business as usual :)

[pawelpabich]

Yes please :). I hope this will help deliver features more often.

[johnsimons]

@pawelpabich are you referring to the issue with threads in SQL transport?

[pawelpabich]

Yes and no. I hope that single version of .NET framework will free some of your time spent on support so you have time to tackle some of the hard problems :) Like the configuration refactoring and multiple endpoints.

[ianbattersby]

+1

[abombss]

+1 to move to 4.5 we need more leverage to get our teams to upgrade their framework versions.

The biggest piece of pushback we will get is from sendonly / publish only endpoints in legacy webapps. Its easy to tell a customer to spin up a new Handler endpoint in 4.5. It will be much harder to get our legacy web apps upgraded just to support Bus.Publish, any thoughts on making a light weight publisher / send only library that doesn't require the full NSB.Core and can run in lower level versions of .net?

[CallumHibbert]

I like the suggestion from @abombss. I too have "send only" legacy web apps running on .NET 4.0, its presently unknown when they might be upgraded.

[johnsimons]

Regarding legacy, v4 endpoints can interact with v5 endpoints.
So what I'm saying is, leave your SendOnly webapps as v4 and upgrade only
the endpoints that you can to v5.
Does this make sense?

On Friday, May 2, 2014, CallumHibbert notifications@github.com wrote:

I like the suggestion from @abombss https://github.com/abombss. I too
have "send only" legacy web apps running on .NET 4.0, its presently unknown
when they might be upgraded.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/2078#issuecomment-42030310
.

[udidahan]

leave your SendOnly webapps as v4

Would this not create a higher level of versioning problems for our customers? Is it really worth it?

[SimonCropp]

@udidahan

Would this not create a higher level of versioning problems for our customers

Not sure how? If a message assembly is left as .net 4 we should be fully compat between NSB v4 and v5

Can you gave some more details?

[udidahan]

What I mean is that now different parts of their codebase need to reference different versions of NSB – as opposed to just using the same version everywhere.

[SimonCropp]

Ok yes. I see what you are getting at.

I dont think @johnsimons was recommending this, he was only saying "we are compat with v4 of NSB". So if organisations do have legacy apps on NSB v4 when they can still make some use of v5.

But I think we need to have some good guidance around this.

[udidahan]

The issue, as I see it, is for ISVs that need to continue to support their customers who may be running older OS versions. It isn’t necessarily an issue of legacy apps.