system.design reference issue of WixSharp on .net 4 - .net-4.0

I'm trying to use WixSharp with .net 4, but I got this warning:
Warning The currently targeted framework ".NETFramework,Version=v4.0,Profile=Client" does not include "System.Design, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" which the referenced assembly "WixSharp, Version=1.0.39.0, Culture=neutral, PublicKeyToken=3775edd25acc43c2, processorArchitecture=MSIL" depends on. This caused the referenced assembly to not resolve. To fix this, either (1) change the targeted framework for this project, or (2) remove the referenced assembly from the project.
I checked that System.Design is not referenced. When I tried to add reference to it, it's actually grayed out in add reference dialog.
As a result, just as the warning says, WixSharp is not resolved, and all namespaces in WixSharp has a missing of reference error.
How should I fix this? compile WixSharp from source?
Fei

Related

Type 'ClientAssertionCertificate' exists in both '...ActiveDirectory.Platform' & '....ActiveDirectory'

I have a cproj which uses the method ClientAssertionCertificate from Microsoft.IdentityModel.Clients.ActiveDirectory. When I do a msbuild at the project level, I'm seeing this strange error.
error CS0433: The type 'ClientAssertionCertificate' exists in both 'Microsoft.IdentityModel.Clients.ActiveDirectory.Platform, Version=3.12.0.827, Culture=neutral, PublicKeyToken=31bf3856ad364e35' and 'Microsoft.IdentityModel.Clients.ActiveDirectory, Version=4.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e3`
I'm sure that I'm referring only the PackageReference Microsoft.IdentityModel.Clients.ActiveDirectory and no references to any other package/assembly which has Microsoft.IdentityModel.Clients.ActiveDirectory.Platform.dll.
Please let me know if any of you are aware of this and can guide me on where in the code should I do the troubleshoot.
I could figure out the issue. A project reference within my project was using a PackageReference to 'IpamAsrExports-master'. This package has the assembly "Microsoft.IdentityModel.Clients.ActiveDirectory.Platform.dll" included within. After I upgraded the package 'IpamAsrExports-master' to a newer version, it resolved the issue.

Azure - Bitbucket deployment failure

I have an asp.net mvc 4 website using continous deployment through Bitbucket on Windows Azure.
I needed to change the account (as it was a test at first), and redeployed using the bitbucket / Azure deployment feature.
But it failed unfortunately :(, it seems "HttpConfiguration" could not be found :O :
Here are the logs of the deployment :
C:\DWASFiles\Sites\mlcpending\VirtualDirectory0\site\deployments\tools\deploy.cmd
Handling .NET Web Application deployment.
D:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1578,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "System.Net.Http.Formatting, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. [C:\DWASFiles\Sites\mlcpending\VirtualDirectory0\site\repository\BienvenueBebe\BienvenueBebe.csproj]
D:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1578,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "System.Web.Http, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. [C:\DWASFiles\Sites\mlcpending\VirtualDirectory0\site\repository\BienvenueBebe\BienvenueBebe.csproj]
D:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1578,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "System.Web.Http.WebHost, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. [C:\DWASFiles\Sites\mlcpending\VirtualDirectory0\site\repository\BienvenueBebe\BienvenueBebe.csproj]
App_Start\WebApiConfig.cs(10,37): error CS0246: The type or namespace name 'HttpConfiguration' could not be found (are you missing a using directive or an assembly reference?) [C:\DWASFiles\Sites\mlcpending\VirtualDirectory0\site\repository\BienvenueBebe\BienvenueBebe.csproj]
An error has occurred during web site deployment.
Handling .NET Web Application deployment.
D:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1578,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "System.Net.Http.Formatting, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. [C:\DWASFiles\Sites\mlcpending\VirtualDirectory0\site\repository\BienvenueBebe\BienvenueBebe.csproj]
D:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1578,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "System.Web.Http, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. [C:\DWASFiles\Sites\mlcpending\VirtualDirectory0\site\repository\BienvenueBebe\BienvenueBebe.csproj]
D:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1578,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "System.Web.Http.WebHost, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. [C:\DWASFiles\Sites\mlcpending\VirtualDirectory0\site\repository\BienvenueBebe\BienvenueBebe.csproj]
App_Start\WebApiConfig.cs(10,37): error CS0246: The type or namespace name 'HttpConfiguration' could not be found (are you missing a using directive or an assembly reference?) [C:\DWASFiles\Sites\mlcpending\VirtualDirectory0\site\repository\BienvenueBebe\BienvenueBebe.csproj]
An error has occurred during web site deployment.
D:\kuduservice\wwwroot\bin\scripts\starter.cmd C:\DWASFiles\Sites\mlcpending\VirtualDirectory0\site\deployments\tools\deploy.cmd
Anyone having these issues too ?
It looks like your solution may not have NuGet enabled. Try right clicking on your solution in VS to enable that, commit the change and then push again.
But I doubt this is related to changing the Bitbucket account.

Where could I get mono's TPL.Dataflow?

I am working with mono-3.0.10 on a Macbook. In the mono 3.0 release note, Tpl.Dataflow is mentioned, and I also noticed that the source code of Tpl.Dataflow is there in mono's github repo master branch.
But I couldn't find it in my local mono install.
logan#Logans-MBA /Library/Frameworks/Mono.framework
{13-06-04 3:47:48} $ find . -name "*.Dataflow.*"
./Versions/3.0.10/lib/mono/4.5/System.Threading.Tasks.Dataflow.dll
logan#Logans-MBA /Library/Frameworks/Mono.framework
{13-06-04 3:59:55} $ file ./Versions/3.0.10/lib/mono/4.5/System.Threading.Tasks.Dataflow.dll
./Versions/3.0.10/lib/mono/4.5/System.Threading.Tasks.Dataflow.dll: broken symbolic link to ../gac/System.Threading.Tasks.Dataflow/4.0.0.0__b77a5c561934e089/System.Threading.Tasks.Dataflow.dll
I have tried reinstall the mono from installer, but no luck.
Then, I tried the dlls downloaded from nuget, the following errors comes:
/Users/logan/Workspace/Camp/Dragon/ClientEventHandlerDemos/DataflowBlockClientEventHandler.cs(11,13): error CS0012: The type `System.Object' is defined in an assembly that is not referenced. Consider adding a reference to assembly `System.Runtime, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
/Users/logan/Workspace/Camp/Dragon/ClientEventHandlerDemos/DataflowBlockClientEventHandler.cs(11,34): error CS0012: The type `System.Action`1<TInput>' is defined in an assembly that is not referenced. Consider adding a reference to assembly `System.Runtime, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
There are 3 editions from nuget, net45, netcore45 and portable-net45. I tried them all, but still no luck.
So, where could I find the right update to date Tpl.Dataflow works with mono?

The type `System.Xml.XmlElement' is defined in an assembly that is not referenced. Consider adding a reference to assembly System.Xml

I tried to import an external library to my project, but I'm receiving an error:
Error CS0012: The type System.Xml.XmlElement' is defined in an assembly that is not referenced. Consider adding a reference to assemblySystem.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
System.XML (2.0.5.0) is added to the project. What can be the problem?
The problem may be that you are using an 'external library'
Is this a library that has been built for Xamarin.iOS? Or is it a more conventional .Net assembly.
Because Xamarin.iOS is based originally on Moonlight (which used the Silverlight assemblies), then you cannot just pull in external assemblies - you should recompile these assemblies specifically for Xamarin.iOS

What do these Mono/xbuild warnings mean and how do I fix them?

I build VS2010 projects with Mono's xbuild 2.10.5.0. The projects use the '.NET Framework 3.5 Client Profile' as the target framework (they must be 3.5 compatible and I don't need more than the client profile parts).
I'm getting the following warnings:
Build succeeded.
Warnings:
c:\Project\MyProject.csproj (default targets) -> C:\PROGRA~2\Mono\lib\mono\4.0\Microsoft.Common.targets (GetReferenceAssemblyPaths target) ->
C:\PROGRA~2\Mono\lib\mono\4.0\Microsoft.Common.targets: warning : Unable to find framework corresponding to the target framework moniker '.NETFramework,Version=v3.5,Profile=Client'. Framework assembly references will be resolved from the GAC, which might not be the intended behavior.
c:\Project\MyProject.csproj (default targets) -> C:\PROGRA~2\Mono\lib\mono\4.0\Microsoft.Common.targets (ResolveAssemblyReferences target) ->
C:\PROGRA~2\Mono\lib\mono\4.0\Microsoft.Common.targets: warning : Reference 'mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' not resolved
C:\PROGRA~2\Mono\lib\mono\4.0\Microsoft.Common.targets: warning : Found a conflict between : 'System' and 'System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. Using 'System' reference.
C:\PROGRA~2\Mono\lib\mono\4.0\Microsoft.Common.targets: warning : Found a conflict between : 'System.Core' and 'System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. Using 'System.Core' reference.
I'm afraid I don't understand these and the only Google hit for "Unable to find framework corresponding to the target framework moniker" is the commit for that error message.
What do these warnings mean and how can I fix them? Is the 'client profile' not supported by Mono at all? If so, I couldn't find anything about that in the Mono documentation. What causes the unresolved mscorlib reference and where are these two System references it reports a conflict between?
You are guessing correctly - Mono does not support the 'Client' profile (e.g. search Mono version of 3.5 Microsoft.Common.targets for any mention of 'Client'), only the full 3.5 and 4.0 profiles. To fix them, you need to specify one of the supported profiles in your project file. Profile selection only restricts the set of references available during build, an assembly compiled with the 'Client' profile will work on the 'Full' profile just fine.
The mscorlib, Version=2.0.0.0 unresolved reference is happening because you are compiling with a 4.0 profile (which is the default fallback). It will disappear once you set your profile to a supported value. If you do not want to change your project file, you can build with xbuild /p:TargetFrameworkProfile="", which correctly chooses the 3.5 set of assemblies.