We're planning to make .NET 4 the minimum requirement for the C#/.NET driver

[Robert Stam]

Dear users,

In the next version or two of the C#/.NET driver we are planning to change the minimum .NET version required from 3.5 to 4. This would allow us to start using (and supporting) new features of .NET 4.

One reason this hasn't been done earlier was to ensure compatibility with Mono, but that is no longer an issue as Mono has been supporting .NET 4 for awhile now.

Another reason this hasn't been done earlier was out of concern that some of our users might not be prepared to move to .NET 4. However, since .NET 4 has been out for such a long time, this should be less of a concern now. Nonetheless, if you would be affected by us raising the minimum requirement to .NET 4 please comment, either here, or better yet on the JIRA ticket:

https://jira.mongodb.org/browse/CSHARP-625

Thank you,

Robert, Craig and Sridhar

The C#/.NET driver team

[Remi Thomas]

Hello Robert,

.NET 4 requires SP3 on XP and some compagny are always on SP2.

This is why all my projects are .NET 3.5

Remi

[Robert Stam]

I find it surprising that a company would standardize on Windows XP SP2.

SP2 for Windows XP was released in August 2004 (more than 8 years ago).

Support for Windows XP SP2 ended July 2010.

That would mean that any company running Windows XP SP2 would not have received any security updates (via Windows Update) in over two years, which seems like a terrible idea.

The dates I quote above are from this web page:

http://www.microsoft.com/en-us/download/details.aspx?id=28

[mongotime]

Yeah, I doubt you're going to lose any clients. We're not talking about a consumer app here.. it's a driver for a database!!

[Remi Thomas]

Hi,

I'm writting a big business app (DAM, OCR, PDF, ...). MongoDB Rocks for company archiving system with fulltext...

First version was in .NET 2.0 so I wrote my own C++/CLI MongoDB driver based on C++ driver.

Now we deploy in .NET 3.5

Anyway this is not a problem to go to 4.0, simply keep current 3.5 driver version available, I'm using very basic API (open, find, save)

Remi

[Justin Dearing]

Robert,

I'm late on the bandwagon, but I'm all for jumping to .NET 4.0, It present a problem for machines running PowerShell 2.0, but there are way around that problem.

Justin

[伟敏胡]

As Mongo2.2.2 is not support XP any more,So I think it is the timing to upgrade to Net 4.0.
By the way ,can you tell me when the driver will upgrade to Net4.0 ,and when the Driver2.0 will realease,thank you.


在 2012年11月8日星期四UTC+8上午2时17分25秒，Robert Stam写道：

[Robert Stam]

The next version of the C# driver is 1.8, and while no release date has been set it should coincide approximately with the release of version 2.4 of the server.

We are not currently planning to require .NET 4 for the 1.8 version of the C# driver.

[Robert Stam]

Can you add a comment to the JIRA ticket:

https://jira.mongodb.org/browse/CSHARP-625

Where it will be more visible and persistent?

Building and supporting two versions of the driver is not something we want to do, and is the main reason we have been delaying so long to start requiring .NET 4, even though .NET 4 has been out for a very long time.

On Fri, Jan 11, 2013 at 11:45 AM, John Wood <john...@dbframework.com> wrote:

Do you intend to continue supporting a version of the driver that will work with .Net 3.5 ?

For a downloadable consumer app, forcing them to have .Net 4 is pretty significant and would cause some to skip the download. So I would like it if a .Net 3.5 version were still available and supported for the foreseeable future...

--
You received this message because you are subscribed to the Google
Groups "mongodb-user" group.
To post to this group, send email to mongod...@googlegroups.com
To unsubscribe from this group, send email to
mongodb-user...@googlegroups.com
See also the IRC channel -- freenode.net#mongodb

[Robert Stam]

We haven't worked out all the details, but we are not planning to require .NET Framework 4 for the upcoming C# driver 1.8 release, so it won't be until some future release that we make the switch.

Once we do make the switch to .NET Framework 4 we would start using the new features of .NET Framework 4 and I don't see how it would be possible to maintain compatibility with older versions of the .NET Framework.

The current versions of Mono are roughly equivalent with .NET Framework 4 and we are planning to continue to maintain compatibility with new enough versions of Mono (but Mono 2.6 would be too old at that point). We are constantly testing Mono compatibility.

Once the driver requires .NET Framework 4 you are going to have to have .NET Framework 4 even if you own application doesn't use any .NET Framework 4 specific features.

On Tue, Jan 22, 2013 at 8:32 PM, <ni...@dreamfiregames.com> wrote:

Dear Robert,

FYI, I'm attempting to use the C# driver in Unity3d, which uses Mono 2.6 and probably will do for awhile. Mono 2.6 is approximately equivalent to .NET 3.5.

If you guys want to use .NET features which Mono 2.6 doesn't implement, perhaps some kind of compatibility guide would be in order so we know what classes or methods to avoid?

Am I right in thinking code will still compile as long as we limit ourselves in such a fashion?

Thanks,

Nicholas
Dreamfire Ltd

[daniel....@nupe.com]

Fine with me. I'm already building it to 4.5.