Problem generating manifest.
"Problem generating manifest. Insufficient memory to continue the execution of the program."
I hate this error. Hate it with a passion. I work on a few Visual Studio projects of fairly large sizes. This error gets triggered from time to time when I perform a project build. It's hard to find a whole lot of information about this online. Solutions vary from resetting your Visual Studio project settings to disabling updates. I don't know if there's really any foolproof solution other than closing the project and re-opening it. Perhaps it's as simple as Visual Studio 2008 having a dreaded memory leak. Every developer faces a memory leak from time to time - certainly Microsoft is no different.
In my particular case, I did find a solution to the problem (which was caused by me).
I had thought it would be useful to link a file from one project to another project. This involves the process of adding an existing file to a new project, and selecting "Add As Link". This seemed convenient because I had a VB.NET form that I needed to share across applications. I went with adding the form as a new link instead of altering my form code and placing it in a DLL. This saved me time. Well, adding the form as a link sort of backfired on me. As it turns out, when you build a project that shares a file with another project - that source project also needs to build. This eats up a ton of memory. I started seeing the "Problem generating manifest..." error every other build. This was, as you can imagine, very annoying. Once I stopped sharing my form across projects - bit the bullet and added it as a DLL that I could import to both projects, my problem went away.
Tags: .net, 2008, add as link, dll, existing file, memory, problem generating manifest, program, settings, shared form, updates, visual studio
Comments
Got something to say?