No .dll file?

Jul 9, 2010 at 6:48 AM

Hi,

 

Is it possible to compile the project in VB.Net so that the additional Fluent.dll file is not required?

 

Thanks!

Coordinator
Jul 9, 2010 at 7:23 AM

I am not good at VB.NET... Well, I think it is not possible

Daniel

Jul 9, 2010 at 7:28 AM
Is there a way you would do it NOT in VB.net?
Coordinator
Jul 9, 2010 at 8:44 AM

Hmm.. copy C# source code in an app project, fix all URI, maybe something else and compile...
But why?

Jul 9, 2010 at 5:03 PM
Edited Jul 9, 2010 at 5:03 PM
You can include all the files of the Fluent project in your own solution/project, but it would be too much work! You might be able to install Fluent to the GAC and have it only in the system-directory so that you don't need to find it or have it in the folder with the application. However, i must agree with daVincis opinion: But why?
Jul 12, 2010 at 8:55 PM

Maybe this could help:

http://research.microsoft.com/en-us/people/mbarnett/ilmerge.aspx

Jul 19, 2010 at 8:28 PM
Thanks tgrand, the thing is I've already tried ILMerge. It doesn't seem to want to merge the Fluent .dll with an exe? Can you give it a shot and tell me what I'm doing wrong? Thanks so much! :)
Jul 24, 2010 at 4:34 PM
Edited Jul 24, 2010 at 4:36 PM
I didn't have much time to try it just now, and I'm writing this message in a hurry, but I got ILMerge to do the merge successfully. I had to run ILMerge in the .NET 4.0 runtime, using the config file linked to on the ILMerge home page. (Save it as ILMerge.exe.config in the same directory as ILMerge.exe.) Then use a command line like this:
"C:\Program Files (x86)\Microsoft\ILMerge\ILMerge.exe" /targetplatform:v4,c:\windows\Microsoft.NET\Framework\v4.0.30319 /out:Merged.exe FluentTest.exe Fluent.dll

However, when I run the merged EXE, it throws an exception:
The component 'FluentTest.App' does not have a resource identified by the URI '/FluentTest;component/app.xaml'.

Apparently ILMerge doesn't work out of the box with WPF assemblies. But it sounds like if you put some effort in, you can probably make it work. See, for example, this page:
http://blog.mahop.net/post/Merge-WPF-Assemblies.aspx

Also, if you want to make your life easier, you can skip ILMerge by throwing some money at the problem:
http://stackoverflow.com/questions/1025843/merging-dlls-into-a-single-exe-with-wpf

Good luck. And if you still need help later, please post in detail what you tried and what happened.