This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: CSharp.dll fails.
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Apr 09, 2012
07:50 PM
CSharp.dll fails.
I am using:
VS 2010 pro
multi-language solution (C# & VB)
.net framework 4
Hello.
When I try to build setup project, the warning below appears.
I re-installed .net framework,
and changed targeted version of all project from 4 client profile to 4 full.
But nothing changes.
System.Dynamic.dll certainly does not exist, for the namespace 'System.Dynamic' is included 'System.Core.dll'.
How can I avoid this warning? Or I should simply ignore it?
== from logfile ==
Adding file 'Microsoft.CSharp.dll' that is a dependency of component 'Component2'
ISEXP : warning -6248: Could not find dependent file System.Dynamic.dll, or one of its dependencies of component Component2
VS 2010 pro
multi-language solution (C# & VB)
.net framework 4
Hello.
When I try to build setup project, the warning below appears.
I re-installed .net framework,
and changed targeted version of all project from 4 client profile to 4 full.
But nothing changes.
System.Dynamic.dll certainly does not exist, for the namespace 'System.Dynamic' is included 'System.Core.dll'.
How can I avoid this warning? Or I should simply ignore it?
== from logfile ==
Adding file 'Microsoft.CSharp.dll' that is a dependency of component 'Component2'
ISEXP : warning -6248: Could not find dependent file System.Dynamic.dll, or one of its dependencies of component Component2
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Apr 10, 2012
07:40 AM
Hi,
The warning 6248 can be overcome by either adding the dependent file to the Primary output location or by adding a reference to their Visual Studio project to the dependent file.
Kindly refer the below KB that elaborates on this warning:
http://kb.flexerasoftware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=Q109065&sliceId=1&docTypeID=DT_ERRDOC_1_1&dialogID=112354397&stateId=0
The warning 6248 can be overcome by either adding the dependent file to the Primary output location or by adding a reference to their Visual Studio project to the dependent file.
Kindly refer the below KB that elaborates on this warning:
http://kb.flexerasoftware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=Q109065&sliceId=1&docTypeID=DT_ERRDOC_1_1&dialogID=112354397&stateId=0