VS8 C# error - "compiler could not be created."

  • Thread starter Thread starter MikeJ
  • Start date Start date
M

MikeJ

In my office, we have workstations with standard Win 2000 images (OS plus
standard apps like Office, etc.) as developers, we then install our
development tools on top of those images. other developers in my office
have installed VS8 and use it with no problems. however, on a new
workstation that I recently got, I have installed VS8, and get this error
whenever I try to access a C# project or create a new C# project:

"Project 'XYZ' could not be opened because the Microsoft Visual C#
compiler could not be created. Please re-install Visual Studio."

I have tried repairing VS, and uninstall/reinstall of VS, with no
resolution, this error does not go away.

Googling on this problem, I've seen messages talking about problems with
the PATH or other environment variable settings, but I've checked them
against functional machines, and they are the same.

I am about ready to have the machine re-imaged clean to try again, but if
anyone here has any insight on how to resolve this problem, I would
appreciate the help.

Thanks.

-- Mike J
 
Hi Mike,
"Project 'XYZ' could not be opened because the Microsoft
Visual C# compiler could not be created. Please re-install
Visual Studio."
Click to expand...

Such a problem also happens when the Visual Studio could not find its
corresponding .NET Framework. In this regards, I suggest you try to
reinstall the .NET Framework 2.0 for a test.

By the way, according to your description, do you mean this problem only
occurs in your virtual machine?

Thanks!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
(e-mail address removed) ("Gary Chang[MSFT]") wrote in
Hi Mike,


Such a problem also happens when the Visual Studio could not find its
corresponding .NET Framework. In this regards, I suggest you try to
reinstall the .NET Framework 2.0 for a test.
Click to expand...

thanks for responding.

tried it. now it's getting weirder. now it alternates between the old
message and a new one: "Attempted to read or write protected memory.
This is often an indication that other memory is corrupt."

I'm running a memory tester on the computer now, but so far the physical
memory is coming up fine.

any other ideas?
By the way, according to your description, do you mean this problem
only occurs in your virtual machine?
Click to expand...

no, the native operating system is win 2000. our PC deployment people
have a standard ghost image that they use to install the OS on new PCs.

-- Mike J
 
Hi Mike,

Thanks for the response!

I have already checked our database for this issue, but I didn't find a
similar case. In this scenario, it appears to be a machine specific
problem. I am afraid you need a re-imaged machine and have a clean Visual
Studio 2005 installation to workaround this problem.

If you have any issues or concerns, please let me know. It's my pleasure to
be of assistance.

Thanks for your understanding.

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
This has become quite aggevating. I just had my development box re-
images with a clean OS plus standard apps, that everyone in my office
has. did nothing else with it. installed VS. same problem, getting the
two error messages (cannot create C# compiler, and corrupt memory.)

decided to try it out with a VB project, same error (cannot create VB
compiler...)

any more help would be appreciated. thanks.

(e-mail address removed) ("Gary Chang[MSFT]") wrote in
 
No idea yet, Mike.

Could that machine run any .Net Framework 2.0's application?

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
(e-mail address removed) ("Gary Chang[MSFT]") wrote in
No idea yet, Mike.

Could that machine run any .Net Framework 2.0's application?
Click to expand...

yes. I just had a co-worker create a little Hello World win-app, and it
runs fine on the troubled computer.
 
Hi Mike,

Based on my experience, there is a similiar issue in VS 2003 when dealing
with project that has long path (under complex folder hierarchy) which is
about to exceed the OS path limitation. Is the project try accessing that
report the error also under a deep folder hierarchy?(like the document
settings ..... my document ......) If so, you can try moving the project
to a driver's root folder and try accessing it again. In addition, you can
also use filemon tool to trace the file system accessing during the VS IDE
opening or creating projects to see whether there is any file accessing
failure.....

Hope this helps a little

Regards,

Steven Cheng
Microsoft Online Community Support


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
 
problem resolved: it was bad memory.

our PC Staging people swapped out the memory, then I uninstalled and
reinstalled VS8, and now it's working.
 
That's a terrible, Mike.

But I am glad to know you found the root cause of this issue. :)

Good Luck!


Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top