Visual C# .NET 2005 express problems

[kimiraikkonen]

Visual C#.NET 2005 express has some issues, unlike VB.NET 2005 has
none of them:

The most annoying one is:
For example if there's a coding error, it must be reported at the
buttom of the screen in "error list" "REAL-TIME". At least, that was
like that in VB.NET 2005 express. But in Visual C# .NET 2005 you won't
be able to aware of coding errors till you press "play" build & run
button.

Unlike in VB.NET 2005 express again, if there's a coding error it must
be reported simultaneously and real-time when you change active line
by clicking anywere with cursor or when you jump somewhere blank with
keyboard. But it doesn't like that, again, errors are reported after
you press build & run button. Thus you cannot be aware of if there's a
coding error till debugging.

Another thing: Don't know SP1 have fixed or not this, if you try to
place shockwave flash object (flash9b.ocx), you get error, this
problem's solution was to rebuild project although the error message,
then running again which was working exactly in VB.NET 2005 express,
which completely did NOT work in Visual C# .NET 2005.

Of course there may be more bugs/problems in VC# 05 but they're
strongly disappointment.

Which other development platform (GUI, with good IDE of course) do you
recommend for Windows based C# development (must include all of
toolbox contols and .NET components (optional)?

Thanks for reading.

 

[Guest]

(See below)

Visual C#.NET 2005 express has some issues, unlike VB.NET 2005 has
none of them:

The most annoying one is:
For example if there's a coding error, it must be reported at the
buttom of the screen in "error list" "REAL-TIME". At least, that was
like that in VB.NET 2005 express. But in Visual C# .NET 2005 you won't
be able to aware of coding errors till you press "play" build & run
button.

You will find that many people, including myself, think this is a positive
thing. There is a feeling that the realtime compiling slows down editing
functions.

Unlike in VB.NET 2005 express again, if there's a coding error it must
be reported simultaneously and real-time when you change active line
by clicking anywere with cursor or when you jump somewhere blank with
keyboard. But it doesn't like that, again, errors are reported after
you press build & run button. Thus you cannot be aware of if there's a
coding error till debugging.

Another thing: Don't know SP1 have fixed or not this, if you try to
place shockwave flash object (flash9b.ocx), you get error, this
problem's solution was to rebuild project although the error message,
then running again which was working exactly in VB.NET 2005 express,
which completely did NOT work in Visual C# .NET 2005.

I haven't used the control, but I saw your other post where you mentioned
this. You might try the beta 2 of VS 2008. To me though, it sounds like
there is a problem with the control rather than VS.

Of course there may be more bugs/problems in VC# 05 but they're
strongly disappointment.

Which other development platform (GUI, with good IDE of course) do you
recommend for Windows based C# development (must include all of
toolbox contols and .NET components (optional)?

No experience here with anything else. Sorry.

 

[kimiraikkonen]

(See below)




You will find that many people, including myself, think this is a positive
thing. There is a feeling that the realtime compiling slows down editing
functions.

Thanks for the response. So you confirm what i meant? (latency about
error-list while coding)

What's the reason of this (Visual C# .net 05) unlike in VB.NET?

Thanks

 

[Peter Duniho]

[...]
Of course there may be more bugs/problems in VC# 05 but they're
strongly disappointment.

It's very difficult to understand what the "bugs" you're writing about
actually are, but I doubt they are really bugs. For sure, the first
two you appear to be complaining about whether compile-time errors can
be seen before trying to run the program. Since simply building the
project does in fact show you errors, it's ridiculous to claim that you
have to run the project to see the error.

It's true that there are some _minor_ differences in the real-time
compilation between VB and C#, but it's pretty silly to argue that the
C# Express product is "buggy" because of these differences.

As far as the handling of a particular OCX goes, your description is
even harder to follow but it doesn't seem likely that OCX support in C#
is broken. More likely you are simply misunderstanding how to use it.

Which other development platform (GUI, with good IDE of course) do you
recommend for Windows based C# development (must include all of
toolbox contols and .NET components (optional)?

I recommend Visual Studio 2005, and am confident that the upcoming 2008
version will be equally good. I have used both the Express version of
2005 and the retail Professional version, and frankly I was surprised
at just how much you get in the free Express version. I certainly
don't agree that "strongly disappointment [sic]" is an appropriate
description of either.

Pete

 

[kimiraikkonen]

[...]
Of course there may be more bugs/problems in VC# 05 but they're
strongly disappointment.

It's very difficult to understand what the "bugs" you're writing about
actually are, but I doubt they are really bugs. For sure, the first
two you appear to be complaining about whether compile-time errors can
be seen before trying to run the program. Since simply building the
project does in fact show you errors, it's ridiculous to claim that you
have to run the project to see the error.

Yes, building is enough to see if there is a failure due to coding
error.

It's true that there are some _minor_ differences in the real-time
compilation between VB and C#, but it's pretty silly to argue that the
C# Express product is "buggy" because of these differences.

I don't call them as "bug" but if this exist if wonder why this
exist. Please do a techical explanation which makes real-time
compiling much more delayed in VC# when compared to Vb.net.

As far as the handling of a particular OCX goes, your description is
even harder to follow but it doesn't seem likely that OCX support in C#
is broken. More likely you are simply misunderstanding how to use it.

If you search the net, this is common with VS.NET, suggesting to link
flash object via webbrowser control.
I managed to overcome the same problem in Vb.net with rebuilding the
project which wasn't helped in C#.
Error message:
"The type or namespace name 'AxShockwaveFlashObjects' could not be
found (are you missing a using directive or an assembly reference?)"

Which other development platform (GUI, with good IDE of course) do you
recommend for Windows based C# development (must include all of
toolbox contols and .NET components (optional)?

I recommend Visual Studio 2005, and am confident that the upcoming 2008
version will be equally good. I have used both the Express version of
2005 and the retail Professional version, and frankly I was surprised
at just how much you get in the free Express version. I certainly
don't agree that "strongly disappointment [sic]" is an appropriate
description of either.

Pete

 

[Peter Duniho]

[...]
I don't call them as "bug" but if this exist if wonder why this
exist. Please do a techical explanation which makes real-time
compiling much more delayed in VC# when compared to Vb.net.

The compilers are completely different. It's not at all surprising
that there might be subtle differences in the user experience with the
IDE that uses the compiler.

If you search the net, this is common with VS.NET, suggesting to link
flash object via webbrowser control.
I managed to overcome the same problem in Vb.net with rebuilding the
project which wasn't helped in C#.
Error message:
"The type or namespace name 'AxShockwaveFlashObjects' could not be
found (are you missing a using directive or an assembly reference?)"

That suggests to me that you've failed to add the OCX as a reference to
your project. Have you tried doing that?

Pete

 

[Guest]

I am not sure of the reason for the realtime compilation in VB but not C#. A
guess would be that VB has it's legacy in previous versions of the BASIC
language, which were interpreters. I think some expect this behaviour.

 

[Matthew Newman]

I have not used Visual Basic much but I have heard about something called
the background compiler in VB. As I understand it your VB compiler is
constantly running which is why you get your errors right away and adding
components doesn't require an explicit compile. There isn't a bug, its just
a feature in VB.

-Matt Newman

 

[Jon Skeet [C# MVP]]

Visual C#.NET 2005 express has some issues, unlike VB.NET 2005 has
none of them:

The most annoying one is:
For example if there's a coding error, it must be reported at the
buttom of the screen in "error list" "REAL-TIME". At least, that was
like that in VB.NET 2005 express. But in Visual C# .NET 2005 you won't
be able to aware of coding errors till you press "play" build & run
button.

I clearly need to try Express again - because in Professional the
editor will certainly warn you about *some* errors before building.
(ReSharper adds to that list, from what I remember - it's hard to know
offhand how much of my experience is due to ReSharper.)

 

[kimiraikkonen]

Except delay about background compiler / or called real-time error
reporting, there's another thing which was included in VB.NET 05
express:

In C# if you type a known object / class wrong accidently, it will not
be corrected automatically. You have to find by yourself:

Example:

Listbox1.items.add("hello") ---> "items" case must be upper -->
"Items" (correct)

That was auto-corrected in VB.NET but sometimes / not always, not
corrected in C#.

Thanks.

 

[DeveloperX]

Except delay about background compiler / or called real-time error
reporting, there's another thing which was included in VB.NET 05
express:

In C# if you type a known object / class wrong accidently, it will not
be corrected automatically. You have to find by yourself:

Example:

Listbox1.items.add("hello") ---> "items" case must be upper -->
"Items" (correct)

That was auto-corrected in VB.NET but sometimes / not always, not
corrected in C#.

Thanks.

Look you have to understand that VB.NET was an abomination developed
to appease the VB6 crowd. VB6 was fantastic in that you could debug
your code while it was running and changes were immediately put into
effect. No restarting. This is why VB.NET allows edit and continue
*and* as a side effect compiles as you edit. VB6 convertees would have
been very very annoyed without edit and continue.

Second c# is case sensitive. This means you could (but should not)
have an object with both an items member and an Items member. For this
reason it shouldn't auto correct. You can however auto complete by
pressing CTRL+Space anywhere in the word. type i and press CTRL+Space
and if there is only one i method it will auto complete, otherwise it
will pop up the available options and allow you to pick. So with an
object that has members called:

items
cows
covers

type i and it will auto complete items, press c and it will offer you
cows and covers in a drop down.