.NET 4?

Hello,

should the current beta (nightly builds) be able to handle .NET 4 projects?
(Because after switching a project from 3.5 to 4.0 I get very weird
warnings and errors, F12 into Object-Browser only targets the 3.5
counterparts).

--
/\/\arkus.

7 comments
Comment actions Permalink

1632 is working OK on a .NET 4 project here  - F12 gets metadata from the right assemblies.  (I don't think reference source is available for .NET4)

Dreadful performance in the XAML editor mind you, but I don't know if that's R# or VS10.

You might want to try some cache clearing and rebuilding.

0
Comment actions Permalink

Will Dean,

1632 is working OK on a .NET 4 project here  - F12 gets metadata from the right assemblies.  (I don't think reference source is available for .NET4)
You might want to try some cache clearing and rebuilding.


This did not help.
For example this line (Entity Framework) compiles:
  context.SaveChanges(SaveOptions.DetectChangesBeforeSave);

but ReSharper complains:
"Argument type 'System.Data.Objects.SaveOptions' is not assignable to
parameter type 'bool'"

ReSharper knows the enum SaveOptions (and coloring is fine) but hitting F12
on SaveOptions jumps into "System.Data.Entity " without finding
the class (of course).

Even when selecting "System.Data.Entity " in "Object Browser" the
content there definitely does not show the 4.0 assembly because the class
System.Data.Objects.ObjectContext does not contain the SaveChanges overload
with parameter type SaveOptions -- only () and (bool), the latter is
obsolete in 4.0

Strange thing -- only my machine? Or a VS2010 bug?

--
/\/\arkus.

0
Comment actions Permalink

Wierd - I've no idea what it is, but all I can say is there isn't a general 'R# doesn't work with .NET 4' problem.  Not that that helps you in the slightest, but it does mean you should probably report this as a bug to JB.

(If you can get the bug reporting to work that is, I couldn't file exception reports last night, some kind of login error)

0
Comment actions Permalink

Hi Will,

Wierd - I've no idea what it is, but all I can say is there isn't a general 'R# doesn't work with .NET 4' problem.  Not that that helps you in the slightest, but it does mean you should probably report this as a bug to JB.


as I found out so far it's a general R# 3.5/4.0 interop problem when older
2.0/3.5 assemblies are used in a 4.0 context -- in my case a 4.0 EXE using
a 3.5 assembly containing the model.

--
/\/\arkus.

0
Comment actions Permalink

Please could you provide small solution which demonstrates this problem?


0
Comment actions Permalink

Eugene,

Please could you provide small solution which demonstrates this problem?


RSRP-170100

--
/\/\arkus.

0
Comment actions Permalink

Thank you. I'll check this issue shortly

0

Please sign in to leave a comment.