bad experience with 2.0 final release?

[Lloyd Dupont]

I downloaded C# express final release last friday.
Previously I was working with 2.0 beta 2.

I had a few libraries which crashed. Presumably because of some missing
function incompatibilities.
Anyway I went over these but now I really hit a wall.

I have, in my project, 1 windows form application and a few dll.
All of them recompiled from scratch.


There is a method I call a few times.
On the 3rd time I get:
BadImageFormatException
An attempt was made to load a program with an incorrect format. (Exception
from HRESULT: 0x8007000B)
at Cook.GUI.RecipeIngredientGridModel.get_NumRows()
at NGui.Grid.GridView.GetPreferredSize(Size proposed) in
F:\MyWork\eCookBook\NGui\Grid\GridView.cs:line 303

Now the documentation from MSDN makes me wonder.. how come such an exception
(BadImageFormat) is thrown from a function in a DLL
1. which is part of my project, I mean the C# source I just compiled
2. which I alread called successfully a few times before this exception!

I though the beta were quite allright, but it seems to me the final release
are not!

 

[Frans Bouma [C# MVP]]

I downloaded C# express final release last friday.
Previously I was working with 2.0 beta 2.

I had a few libraries which crashed. Presumably because of some
missing function incompatibilities.
Anyway I went over these but now I really hit a wall.

I have, in my project, 1 windows form application and a few dll.
All of them recompiled from scratch.


There is a method I call a few times.
On the 3rd time I get:
BadImageFormatException
An attempt was made to load a program with an incorrect format.
(Exception from HRESULT: 0x8007000B)
at Cook.GUI.RecipeIngredientGridModel.get_NumRows()
at NGui.Grid.GridView.GetPreferredSize(Size proposed) in
F:\MyWork\eCookBook\NGui\Grid\GridView.cs:line 303

Now the documentation from MSDN makes me wonder.. how come such an
exception (BadImageFormat) is thrown from a function in a DLL
1. which is part of my project, I mean the C# source I just compiled
2. which I alread called successfully a few times before this
exception!

I though the beta were quite allright, but it seems to me the final
release are not!

Did you follow the precise explanation how to remove beta2 from your
system prior to install the RTM version? It's key you remove beta2
correctly before installing RTM.

Frans

--

 

[Lloyd Dupont]

Did you follow the precise explanation how to remove beta2 from your

system prior to install the RTM version? It's key you remove beta2
correctly before installing RTM.

I used the (optional) uninstall tool.
Anyway I'm going to try to write a simple sample and I'll submit to the
feedback center..

 

[Wiktor Zychla [C# MVP]]

I used the (optional) uninstall tool.
Anyway I'm going to try to write a simple sample and I'll submit to the
feedback center..

when you have it please share it with rest of us.
since I have found this:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=125454&SiteID=1

I am really interested if similar bug exists in the c# compiler.

Wiktor Zychla

 

[Lloyd Dupont]

here you go:
http://lab.msdn.microsoft.com/produ...edbackid=eb24881a-87b3-41f3-942c-1c9c944ec03e

 

[Wiktor Zychla [C# MVP]]

here you go:

http://lab.msdn.microsoft.com/produ...edbackid=eb24881a-87b3-41f3-942c-1c9c944ec03e

thanks, I confirm the bug and I've validated it on the mdsn page.
Wiktor

 

[Guest]

The only problem that I found was when I tried to debug a web service from
VS2003 I was unable to attach to the iis asp_net process. I have not found a
workaround to this yet.

 

[Lloyd Dupont]

Yeepee....
They have finally acknowledged the bug.
But are still investiagting (looks like it's difficult to fix).
At least I now know for sure they are motivated to fix it.
I hope they will have a downloadable bug fix under 1 month :S

 

[Lloyd Dupont]

Here is a post from Microsoft:
Our investigation is still continuing but we have identified a possible
workaround.

The bug occurs while processing the "where T:class" constraints. Commenting
out
the two "where T:class" clauses from your simplified repro gets us past the
ImageFormat
exception. Avoiding the use of "where" should allow you work around this bug
while we address the runtime issue.

Thanks for alerting us to this issue.