ResGen error

[alkhaef]

Hi all...

Does anyone know where on earth to find the corflags executable?

I'm trying to build on my 64-bit machine, and it's not in the path "C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin". I've tried reinstalling SDKs, but no luck .

Alternately, does anyone know of another workaround?

Thanks again,
Al

[jordansparks]

Do you have dotNet 3.5 installed? How far do you get down your path before you can't go anymore? Is C:\Program Files (x86)\Microsoft SDKs\Windows present?

[alkhaef]

Hi Doc,

Thanks for the quick reply.

Yes, I have .net 3.5 - i believe SP1 (not at that machine now). I have the entire path. It's just that the executable is missing. I even tried a deep search in "Program Files" and "Program Files (x86)", but couldn't find it.

Best,

[jordansparks]

Then I really have no idea. Maybe google to see if anyone else is missing that file too?

[alkhaef]

Thanks anyway. I already googled till I ran out of keywords... Maybe I'll ask Microsoft.

[alkhaef]

FYI for any later viewers...

A reboot made corflags appear . Then, the ResGen fix on the OD site worked .

[B.Thomas]

I kept having the Resgen.exe error as well. I followed the directions on the Open Dental Source Code page;

http://www.opendental.com/manual/sourcecode.html

After Line 3 I had a problem:

3. Copy and paste:
Corflags /32Bit+ /Force ResGen.exe
then Enter. If successful, you will see about 5 lines of text, including "warning CF011: The specified file is strong name signed".


Instead I received the response; "Corflags is not recognized as an internal or external command"

So I researched Corflags and it brought me to the MSDN site where it says;

Where to get corflags.exe. It comes as part of Visual Studio 2010. Open up a "Visual Studio Command Prompt" (not a normal command prompt, as the path won't be set up), and you can call it.


I am currently using C# Express. So my assumption is that the express version will not compile Open Dental and the full version of Visual Studio is required.

[alkhaef]

Hello Dr. Thomas,

Honestly, it's been too long for me to remember how I got out of it, but I can tell you this much - Express should be just fine. I've built OD with express plenty.

Good luck!

Best,
Al

[jordansparks]

I think it just means you are not yet in the folder where corflags resides. We gave two possible paths, but Express might have installed things in slightly different locations. You have to hunt for it.

[B.Thomas]

This is the first time I am attempting to build OD on my new Windows 7 64 bit machine so I'm guessing it may be related to the operating system.

[Creation125]

I am also getting the error "Corflags is not recognized as an internal or external command" on my Windows 7 Professional computer. I looked in the folder "C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin", but Corflags is not there. I am also running using C# Express.

If anyone has a solutions, please post. I've been working on this for 2 hours with nothing working.

[jordansparks]

And you did a search for corflags on your computer?

[jordansparks]

OK, I posted a copy of corflags.exe for you to download and try. Let me know how it goes.

[Creation125]

Where can I find the corflags file to download?

[jordansparks]

http://www.opendental.com/manual/sourcecode.html

[Creation125]

Thanks for the file. Downloaded to fold and renamed to .exe file. Unfortunately, did not work with the following error:

Unsupported 16-bit Application
The program or feature "\??\C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\corflags.exe" cannot start or run due to incompatibility with 64-bit versions of Windows. Please contact the software vendor to ask if a 64-bit Windows compatible version is available.

[afeuer]

I had the same problem. Install this first. http://www.microsoft.com/download/en/co ... px?id=8279
Then I found it here: C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin

I'm running windows 7 64bit.

I ran the fix in the source code page and it gave the CF011 error and everything. I've tried so many different fixes I've found online. I just find it easier to compile OD on one of my 32bit workstations. Sucks, but I've already spent many hours trying to fix that stupid error.

-Adam

[jordansparks]

So are you saying that the link you posted is a fix?

[Creation125]

I'll give it a try tonight.

[afeuer]

sorry I forget to look in this forum every once and a while. I was just sending the link showing where to find the coreflags.exe. I still can't compile it on a 64 bit machine. I've completely given up and only do it on 32 bit systems.

-Adam

[jordansparks]

Hmm. We all have 64 bit machines here. I just don't know.

[jsalmon]

This doesn't have to do with the ResGen.exe error but I ran across this the other day and since the word ResGen was in the file section of the error, I figured it might help someone else browsing for related ResGen issues. The solution is to make sure you have all projects set to build within the solution's Configuration Manager (UnitTest, WebForms and WebHostSynch are optional if you don't want to build them).
Error description was: "Caught a FileNotFoundException saying "Could not load file or assembly ' [path to a specific dll] ' or one of its dependencies. The system cannot find the file specified." The file was: "ResGen" The project was: "OpenDental"

[Creation125]

I couldn't make it run either, and have also given up.

[ZagGrad]

I'm just starting to look into building some plug-ins for OD, but ran into similar problems. I'm new to C# and Visual Studio Express though, so that could be a big part of the problem. Anyway, after digging around for a while I found this on the MSDN link that Jordan posted:

Workaround 3:

Force the CLR to load all MSIL applications as 32-bit by:

1. Cd “%windir%\Microsoft.NET\Framework64\v2.0.50727”

2. Ldr64.exe setwow

Then, since this also is a way to force ResGen.exe to execute as though it’s a 32-bit process, you must also go through the second part of Workaround 2 (setting ResGenToolArchitecture=Managed32Bit).

Pros: Doesn’t require changing the architecture of the referenced assembly

Cons: Affects how the CLR works for the entire machine. Also the same cons as Workaround 2.

Keep in mind, I have Visual C# 2010 Express installed on a Windows 7 64 bit machine. After I followed these instructions the resgen build errors went away. I still have quite a few warnings to take care of, but the solution successfully builds. So I'm on the right path. A word of warning, however: I have absolutely no idea what this did to the compile process or how it might affect any other projects.

[drtech]

I tried this yesterday and it didn't work, now I tried it today (after trying many other things and restarting) and now it complies! Yeah! I spent literally 6 hours yesterday trying to get it to work again on my new install of windows on my same 'ol laptop!