Entity Framework in C# Express 4 (2010)
- I've installed C# 2010 Express and I don't seem to have the ADO.Net template so I can't add an entity frame work .edmx file. I recall when I first converted the previous C# 2008 Express project that I could refresh the EF model and change the mappings but I was making plenty of changes to the underlying database so I decided to delete the existing model (brought across from 2008) and add it afresh in 2010.
However when I go Add / New Item ... I don't get an ADO.NET Template!?
Please help!
Mr Foo- Moved byHarry ZhuMSFTTuesday, November 10, 2009 9:22 AM (From:Visual C# Express Edition)
Answers
- Hi Bei
I found some time and reinstalled everything yesterday and it works now - I've got the Entity Designer in C#2010 Express Beta 2. C#2008 Express is also on same machine. Vista platform.
To get it working I removed everything related to the orignial C#2010 Express Beta install including the SQL Server bits.
Then I restarted the installation (3rd attempt) of C#2010 Express B2.
I note that the "ADO.Net component" is after the "Validate SQL Server" step.
My very uneducated guess is:
Install 1 - failed at "Validate SQL Server" due to named pipes disabled or some other setting in SQL Server.
Install 2 - (after enabling named pipes) I2 incorrectly said everything was ok. (this could also have been a priveleges problem because I1 as user, I2 & I3 as admin.)
Install 3 - worked, but only after completely removing everthing in I1 & I2.
I guess the message for anyone else thinking of installing C#2010 Express B2 is - yes you should get fully functional Entity Designer (ie this has not been crippled in the Express version)
Sorry to bother you - thanks
Mr Foo- Marked As Answer byMr Foo Saturday, November 14, 2009 7:27 PM
All Replies
Did you install VC# 2101 Express Beta1 or Beta2? Also, did you install other VS SKUs SxS with it, and ran into any uninstallation?
Please let me know.
Thanks
BeiHi Bei
I installed C#2010 Beta 2 only.
1st attempt failed when it tried to link in with SQL 2008 Express.
To fix this I enabled Named Pipes + another setting in SQL Manager.
I'm assuming this fixed it because for my 2nd attempt I logged in as Vista admin and this attempt appear to work. (Could be admin log in was actual root cause of 1st failed attempt)
MSI (s) (C0:64) [06:33:59:746]: Note: 1: 1707
MSI (s) (C0:64) [06:33:59:746]: Product: Microsoft Visual C# 2010 Express Beta 2 - ENU -- Installation completed successfully.MSI (s) (C0:64) [06:33:59:747]: Windows Installer installed the product. Product Name: Microsoft Visual C# 2010 Express Beta 2 - ENU. Product Version: 10.0.21006. Product Language: 1033. Installation success or error status: 0.
[Extract from dd_VSMsiLog3EFE.txt]
I still have C#2008 Express on the machine, which I have now rolled back to.
Thanks
Mr Foo- You mean you install VS C#2008, then install VS C# 2010 Beta2 on top of it, right?
Thanks
Bei - Hi Bei
I found some time and reinstalled everything yesterday and it works now - I've got the Entity Designer in C#2010 Express Beta 2. C#2008 Express is also on same machine. Vista platform.
To get it working I removed everything related to the orignial C#2010 Express Beta install including the SQL Server bits.
Then I restarted the installation (3rd attempt) of C#2010 Express B2.
I note that the "ADO.Net component" is after the "Validate SQL Server" step.
My very uneducated guess is:
Install 1 - failed at "Validate SQL Server" due to named pipes disabled or some other setting in SQL Server.
Install 2 - (after enabling named pipes) I2 incorrectly said everything was ok. (this could also have been a priveleges problem because I1 as user, I2 & I3 as admin.)
Install 3 - worked, but only after completely removing everthing in I1 & I2.
I guess the message for anyone else thinking of installing C#2010 Express B2 is - yes you should get fully functional Entity Designer (ie this has not been crippled in the Express version)
Sorry to bother you - thanks
Mr Foo- Marked As Answer byMr Foo Saturday, November 14, 2009 7:27 PM
- BTW - any chance of being able to download the complete install package instead of installing over the NET. It makes life very difficult when you have to re-install due to problems with original install. Mr Foo

