Vc++2005

[ski2sky]

Hi guys,
Why do errors have to be 'zombie' instead of telling the developer exactly what went wrong?
1. Create a simple MFC project;
2. Add a C++ class with the wizard;
3. Remove the class files from the project by right-clicking the files in Solution Explorer and choosing 'Remove' to remove from project;
4. Rename the files in the project folder;
5. Try to add a class with the same name to the project;
The IDE will only generate an empty header file and will give the error msgbox: "Cannot access data for the desired file since it is in a zombie state."
I'm using VS2005 Pro.
What am I doing wrong?
Thanks,
Harry

[Cielak]

You are doing wrong using VS 2005. I can assure you this is only the tip of the iceberg what you are experiencing now. Drop it or you spend most time struggling with various bugs, not writing code.

[ski2sky]

I too, have found other inconsistencies and bugs in the tool when used to develop VC++ projects. I hope that there will be soon a service pack to address those issues.
1. Is there a central place where developers can report bugs pertaining to VC++2005?
2. What are the alternatives to using VC++2005?
Thanks,
Harry

[greg_dolley]

1. Create a simple MFC project;
2. Add a C++ class with the wizard;
3. Remove the class files from the project by right-clicking the files in Solution Explorer and choosing 'Remove' to remove from project;
4. Rename the files in the project folder;
5. Try to add a class with the same name to the project;
The IDE will only generate an empty header file and will give the error msgbox: "Cannot access data for the desired file since it is in a zombie state."
I'm using VS2005 Pro.
What am I doing wrong?
Thanks,
Harry

When you say, "same name", do you mean the same name as the files you removed in step 3, or some other files? I suspect that VS is not removing the reference to the removed files from the project file. Maybe you should force it to save the project file, then try adding the files again.

-Greg Dolley

[Den0x]

Microsoft has a site for reporting bugs in developers tools. You will need some patience and luck if you want to find it.
There is no practically no alternative to VS 2005 if you program for Windows (except the older versions). It is absolutely not so bad - I've been working with Vsual Studio since VS 97 and each release is getting better (but heavier).
IMHO, VS 2005 is by far the best tool for Windows development. I do not know any serious bugs in it. Except Intellisense everything works flawless, the Intellisense is not perfect but still incomparably better than any competiting tool offers.
Someone mentioned there are a lot of bugs in VS - a couple of real examples, please.

[Zaccheus]

You are doing wrong using VS 2005. I can assure you this is only the tip of the iceberg what you are experiencing now. Drop it or you spend most time struggling with various bugs, not writing code.

I have found VS 2005 to be relatively good.

[Chazwazza]

I quite like VS 2005, I've started using it over 2003. (I wanted to give Code::Blocks a go, but the compiler/debugger didn't work properly)

[greg_dolley]

I think VS 2005 has some cool features (such as those really nice debug tooltips when you hover over variables and the different "viewers" like DataSet viewer, XML viewer, text viewer, etc.). However, like everyone else, I have found a couple of bugs -- syntax color settings for brace match box and brace match text don't match what you select; sometimes the compiler will refuse to copy your exe to another location via a Post-Build command (it just says permission denied; the bug disappears after a few tries).

Greg Dolley