Cs0013 Unexpected Error Writing Metadata To File
Contents |
'Not enough storage is available to complete this operation' Visual Studio Development > MSBuild Question 0 Sign in to vote We have a Visual Studio 2010 solution running with just unexpected error writing metadata to file not enough storage 3-4 projects in the solution. This is a Windows Server 2008 32 Bit OS
Unexpected Error Writing Metadata To File C#
and 4GB RAM. More often when building the solution, the error "fatal error CS0013: Unexpected error writing metadata to file no logical space left to create more user strings 'Not enough storage is available to complete this operation" occurs and it fails the build. A general research talks only about similar errors in VS 2005 and the fix to apply SP1. But its suprising the error is continuing even in VS 2010. Any recommended solutions would be appreciated! Wednesday, January 05, 2011 1:42 PM Reply | Quote All replies 0 Sign in to vote Hi Harish, Thanks for your post. Let's scope this issue first. · As far as I know, it seems like a VS2010 IDE or environment issue, but non elimination a problem from your project. Could you please try to build it on another machine/environment? If it doesn't happen, I suppose it is caused by your VS IDE or environment, or not enough space in your hard disk? you can provide a diagnostic build log file via skydrive or email, and we can have a check on it. If it happens again, then I think it can be aresource problemor something related in your project, you can provide a build log as well. Looking forward to your reply. Best Regards, Ziwei Chen MSDN Subscriber Support in Forum If you have any feedback on our support, please contact msdnmg @ microsoft.com Ziwei Chen [MSFT] MSDN Community Support | Feedback to us Get or Request Code Sample from Microsoft Please remember to mark the replies as answers if they help and unmark them if they provide no help. Thursday, January 06, 2011 7:23 AM Reply | Quote 0 Sign in to vote I get the same issue constantly. It is resolved by simply closing down Visual Studio then restarting it. A tremendous annoyance (given that we are talking twenty or thirty times a day!), but it works. I read this posting because I'm hoping to find a better solution
Support Query Forum Release Notes FAQ COMPANY Company News & Events Product Roadmap Contact Us Careers Customers Testimonials Partners Unexpected error writing metadata to file (CS0013) : General Questions Download Trial Home»Forum»General»General Questions Login Register Ranorex FAQ Unexpected error writing metadata to file (CS0013) Ask general questions here. Topic locked 3 posts • Page 1 of 1 Unexpected error writing metadata to file (CS0013) by Gav » Thu Nov 10, 2011 3:18 pm When attempting to run a test I'm getting the following error message:Unexpected error writing metadata to file '[path to .exe]' -- 'No logical space left https://social.msdn.microsoft.com/Forums/vstudio/en-US/e1ddf242-7d5d-4b7d-ac84-9f60c10569e6/fatal-error-cs0013-unexpected-error-writing-metadata-to-file-not-enough-storage-is-available-to?forum=msbuild to create more user strings.' (CS0013)I know that there are a couple of solutions alluded to in this post: http://www.ranorex.com/forum/error-cs0013-no-logical-space-left-t2668.html but I'm using recordings rather than code modules, have plenty of disc space and there are no .dll name conflicts.Is this purely down to the number of images validated against in the overall project (about 30)?If so, is the only solution to create a new project http://www.ranorex.com/forum/unexpected-error-writing-metadata-to-file-cs0013-t2795.html for further tests? Does this mean having to create a new repository? I've tried creating a new project within my existing solution and linked the repo, but get the same error message.Having just bought a premium license, I'm now a little concerned that there are some restrictions that will be problematic to work around.Thanks,Gav Gav Posts: 27Joined: Thu Oct 20, 2011 10:52 am Top Re: Unexpected error writing metadata to file (CS0013) by Support Team » Fri Nov 11, 2011 11:34 am Hi,Is this purely down to the number of images validated against in the overall project (about 30)?Just to make sure that it is the problem with the exceeded number of string literals, can you try to split up your modules/recordings or your solution?As mentioned in the other forum post, it is not a Ranorex limitation, there is just a limit on the number of strings in an assembly.If so, is the only solution to create a new project for further tests? Does this mean having to create a new repository? I've tried creating a new project within my existing solution and linked the repo, but get the same error message.If you have to
Post your question and get tips & solutions from a community of 418,472 IT Pros & Developers. It's quick & easy. Unexpected error writing metadata. WTF? P: n/a Rüdiger Klaehn I https://bytes.com/topic/c-sharp/answers/260932-unexpected-error-writing-metadata-wtf am getting this very annoying error CS0013 whenever I try to build a complex library. I had the problem a few months ago, and followed the advice from the knowledge base and reinstalled visual studio. Now I have a fresh install of WinXP pro, a fresh install of VS.NET 2003, and yet the same problem occurs again! The problem persists even when I do not use visual studio. I am currently consolidating unexpected error my build process using nant, and the same problem occurs. I have searched the net and found many people having the same problem, but not a single solution. Somebody please help me. This is getting quite urgent. best regards Rüdiger Nov 16 '05 #1 Post Reply Share this Question 8 Replies P: n/a Nicholas Paldino [.NET/C# MVP] Rüdiger, I would compare what VS.NET is using to compile versus using NAnt. Basically, check unexpected error writing the command line that VS.NET is using (which is in the output window when you build), and then check out the command line that NAnt is using for the same project. You might be able to see some differences there which might account for the CS0013 error. Also, if you have the luxury of waiting, or working with beta products, you might want to try out VS.NET 2005, and the MSBUILD system. The IDE and the command line builder use the same engine, and you won't have to worry about divergence between the IDE and command line tools. Hope this helps. -- - Nicholas Paldino [.NET/C# MVP] - mv*@spam.guard.caspershouse.com "Rüdiger Klaehn"