ILMerge icon indicating copy to clipboard operation
ILMerge copied to clipboard

Windows 10

Open AlexChea opened this issue 8 years ago • 18 comments

hi, the latest dot net 4.7 is not support

AlexChea avatar May 26 '17 08:05 AlexChea

Could you please be more specific? How is it not supported? If you can provide a repro, that would be best. Thanks!

mike-barnett avatar May 26 '17 16:05 mike-barnett

.net 4.7 exe/dll merge works fine for me!

Fabi avatar May 30 '17 08:05 Fabi

I might have the same issue, tried out the ILMerge GUI tool and I'm getting an error that "Cannot merge .Net 4.7 with ILMerge." although could be related to the tool and not ILMerge itself.

RicardoASilva avatar May 30 '17 08:05 RicardoASilva

It's related to the GUI I think, because I had the same problems there, but it works fine with the command line version

Fabi avatar May 30 '17 12:05 Fabi

I see, i am using GUI to merge too, will try using command line. thanks @Fabi

AlexChea avatar May 31 '17 01:05 AlexChea

Please just update your minor version of framework to 7. For who would like to use ilmergeGUI. Get from this repo https://github.com/jpdillingham/ILMergeGUI, this guy made the fix and is worked.

It's a simple fix,

michaelfp avatar Aug 29 '17 22:08 michaelfp

is it possible to use ilmerge in Windows 10 to merge into dot net 4.6?

AlexChea avatar Oct 16 '17 03:10 AlexChea

Windows 10 should have nothing to do with it: the only thing that should matter is the version of .NET that you have. I am not aware of any problems with 4.6. If you have a (small) repro of any problem, please send it to me.

mike-barnett avatar Oct 16 '17 15:10 mike-barnett

@AlexChea, yes it´s possible! If you have only 4.6 version installed worke as well. But if you have already installed 4.7 need to get from the repo above.

michaelfp avatar Oct 16 '17 19:10 michaelfp

Since I have nothing to do with the GUI, it would help me a lot if people would use this site for issues having to do with ILMerge itself. Thanks!

mike-barnett avatar Oct 16 '17 20:10 mike-barnett

@mike-barnett correct. I´m just trying to help. With run the ilmerge.exe in command-line work´s great in Windows 10.

michaelfp avatar Oct 16 '17 20:10 michaelfp

Sorry! I didn't mean that to sound nasty. I'm super appreciative of your help. I just meant that I can be more efficient if I know whether an issue is about ILMerge itself or the GUI.

mike-barnett avatar Oct 16 '17 20:10 mike-barnett

@mike-barnett in Windows 10, merge gui did not provide option for dotnet 4.6.x, only dotnet 4 how to make it available?

AlexChea avatar Oct 17 '17 03:10 AlexChea

I'm sorry, but I really do not know anything about the GUI. Those questions should be addressed to its author. If you're using the command line (or in-memory API), then you would use the /targetplatform option to tell ILMerge which .NET version to use.

mike-barnett avatar Oct 17 '17 15:10 mike-barnett

On windows 10, I have the same error with the latest version

image

weedkiller avatar Oct 26 '17 00:10 weedkiller

That seems like a problem with the GUI, not ILMerge. Please report it to the author of that tool. Thanks!

mike-barnett avatar Oct 26 '17 02:10 mike-barnett

@weedkiller You're in the wrong issues site. See https://bitbucket.org/wvd-vegt/ilmergegui/issues/1/net-47-framework-support

jnm2 avatar Oct 26 '17 12:10 jnm2

To solve this problem simply go in source code at line 1192 and add the condition: ilmergegui

Whoever does not want to have this job, I've compiled a version fixing the bug: ILMergeGui.zip

3Tecnos-Development avatar Jan 30 '18 12:01 3Tecnos-Development