PCL, Shared projects and WinRT client apps

Tim Heuer

30 May, 2014 10:26 AM

This service is awesome! I have two OSS projects I am trying to hook up, one is a client library using WinRT/XAML. The build error is:
C:\projects\callisto\src\Callisto\Callisto.csproj(253,3): error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\WindowsXaml\v12.0\Microsoft.Windows.UI.Xaml.CSharp.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.

The second is a PCL library which uses shared projects (new) and it fails completely:
C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets(989,5): warning MSB3644: The reference assemblies for framework ".NETPortable,Version=v4.5,Profile=Profile259" were not found. To resolve this, install the SDK or Targeting Pack for this framework version or retarget your application to a version of the framework for which you have the SDK or Targeting Pack installed. Note that assemblies will be resolved from the Global Assembly Cache (GAC) and will be used in place of reference assemblies. Therefore your assembly may not be correctly targeted for the framework you intend. [C:\projects\taglib-sharp-portable\src\TagLib.Portable\TagLib.Portable.csproj]
10C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets(1635,5): warning MSB3270: There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscorlib.dll", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project. [C:\projects\taglib-sharp-portable\src\TagLib.Portable\TagLib.Portable.csproj]
11c:\projects\taglib-sharp-portable\src\TagLib.Shared\TagLib\FileTypes.cs(27,14): error CS0234: The type or namespace name 'Linq' does not exist in the namespace 'System' (are you missing an assembly reference?) [C:\projects\taglib-sharp-portable\src\TagLib.Portable\TagLib.Portable.csproj]

Any Ideas on how to resolve these?

  1. #1 Posted by Scott Dorman on 30 May, 2014 12:47 PM

    I have the same problems with building a PCL project as Tim is having. There also seems to be other missing assemblies, as I get errors about not being able to find Linq, ComponentModel, RegularExpressions, DataContract, DataMember, and several others.

    This either needs to be resolved or we need the ability to add these libraries into the build environment or this isn't a usable solution.

  2. #2 Posted by Feodor Fitsner Support staff on 30 May, 2014 01:39 PM

    Hi guys,

    We are going to deploy a new build worker image today with Windows apps support and PCL assemblies.

    - Feodor

  3. #3 Posted by Scott Dorman on 30 May, 2014 02:12 PM

    Great to hear! Can you please let us know when the new build worker image is deployed? I'd like to test out my failing project once it is.

  4. #4 Posted by Feodor Fitsner Support staff on 30 May, 2014 02:19 PM

    Sure, I'll do!

    - Feodor

  5. #5 Posted by Feodor Fitsner Support staff on 30 May, 2014 08:03 PM

    It's done. There is a new build worker image based on Windows Server 2012 R2 (and it's default now) with Windows apps support and PCL installed.

    Both projects work like a charm (though cadru is failing due to failed tests)!

    cadru:

    taglib-sharp-portable:

  6. #6 Posted by Scott Dorman on 31 May, 2014 12:14 AM

    Thanks! I fixed the failing unit tests and everything builds just fine.

  7. #7 Posted by Feodor Fitsner Support staff on 31 May, 2014 12:44 AM

    Cool, thanks for the update!

    - Feodor

  8. #8 Posted by Tim Heuer on 31 May, 2014 01:59 AM

    Thanks Feodor!

  9. #9 Posted by Scott Dorman on 06 Aug, 2014 09:05 PM

    I think this can be closed. I know this fixed my build issues and it sounds like it also fixed Tim's issues as well.

  10. #10 Posted by Feodor Fitsner Support staff on 07 Aug, 2014 01:00 AM

    OK, thanks for the update.

    - Feodor

  11. #11 Posted by bniemyjski on 03 Mar, 2015 03:21 AM

    How'd you fix this issue? I'm also seeing this on our project: https://github.com/exceptionless/Exceptionless.net

  12. #12 Posted by Feodor Fitsner Support staff on 03 Mar, 2015 03:50 AM

    What errors/warnings do you get?

  13. #13 Posted by bniemyjski on 03 Mar, 2015 03:59 AM

    Building Exceptionless.Mvc (NET45)
    Microsoft (R) Build Engine version 12.0.31101.0
    [Microsoft .NET Framework, version 4.0.30319.34209]
    Copyright (C) Microsoft Corporation. All rights reserved.

    C:\Program Files
    (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets(991,5):
    warning MSB3644: The reference assemblies for framework
    ".NETFramework,Version=v4.5,Profile=Client" were not found. To resolve
    this, install
    the SDK or Targeting Pack for this framework version or retarget your
    application to a version of the framework for which you have the SDK or
    Targeting Pack installed. Note that assemblies will be resolved from the
    Global Assembl
    y Cache (GAC) and will be used in place of reference assemblies. Therefore
    your assembly may not be correctly targeted for the framework you intend.
    [C:\projects\exceptionless-net\Source\Extras\Exceptionless.Extras.csproj]
    Exceptionless ->
    C:\projects\exceptionless-net\Build\Release\Exceptionless.Mvc\lib\net45\Exceptionless.dll
    C:\Program Files
    (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets(1697,5):
    warning MSB3270: There was a mismatch between the processor architecture of
    the project being built "MSIL" and the processor architecture of
    the reference
    "C:\Windows\Microsoft.NET\Framework\v4.0.30319\\mscorlib.dll", "x86". This
    mismatch may cause runtime failures. Please consider changing the targeted
    processor architecture of your project through the Configuration
    Manager so as to align the processor architectures between your project and
    references, or take a dependency on references with a processor
    architecture that matches the targeted processor architecture of your
    project. [C:\proje
    cts\exceptionless-net\Source\Extras\Exceptionless.Extras.csproj]
    Exceptionless.Extras ->
    C:\projects\exceptionless-net\Build\Release\Exceptionless.Mvc\lib\net45\Exceptionless.Extras.dll
    Exceptionless.Mvc ->
    C:\projects\exceptionless-net\Build\Release\Exceptionless.Mvc\lib\net45\Exceptionless.Mvc.dll

    Thanks
    -Blake Niemyjski

  14. #14 Posted by bniemyjski on 03 Mar, 2015 04:01 AM

    Exceptionless.dll is a pcl library.

  15. #15 Posted by Feodor Fitsner Support staff on 03 Mar, 2015 04:20 AM

    Just checked - both "test" projects having PCL libraries are still building fine.

    Cadru:
    Build results: https://ci.appveyor.com/project/FeodorFitsner/cadru
    PCL .csproj file: https://github.com/scottdorman/cadru/blob/master/src/Cadru.Core/Cad...

    taglib-sharp-portable:

    https://ci.appveyor.com/project/FeodorFitsner/taglib-sharp-portable
    PCL .csproj file: https://github.com/FeodorFitsner/taglib-sharp-portable/blob/master/...

    786C830F-07A1-408B-BD7F-6EE04809D6DB project type guid means "Portable Class Library".

    There might be something else with Exceptionless.

  16. #16 Posted by Feodor Fitsner Support staff on 03 Mar, 2015 04:30 AM

  17. #17 Posted by bniemyjski on 03 Mar, 2015 01:01 PM

    Yeah, I see you still get that error too when building the mvc project: https://ci.appveyor.com/project/FeodorFitsner/exceptionless-net

  18. #18 Posted by bniemyjski on 03 Mar, 2015 02:02 PM

    Is there any way to specify that I want to use msbuild from .NET framework 4.5.1/4.5.2? In psake we did this by setting the Framework Version at the top of our powershell script:

    http://mattrandle.me/psake-net-4-5-2-and-msbuild/

  19. #19 Posted by bniemyjski on 03 Mar, 2015 02:16 PM

    I set the environmental version to vs2013 but it didn't remove the error either.. Wonder what is causing this issue.

  20. #20 Posted by Feodor Fitsner Support staff on 03 Mar, 2015 03:48 PM

    Will take a look.

  21. #21 Posted by Feodor Fitsner Support staff on 03 Mar, 2015 07:13 PM

    Blake,

    I've cloned the project to my dev machine and I'm getting the same output (warnings on MVC project) while trying to build it. See attached.

    I have VS 2013 Ultimate with Update 4.

  22. #22 Posted by Feodor Fitsner Support staff on 03 Mar, 2015 11:09 PM

    Is that a regular MVC project?

  23. #23 Posted by bniemyjski on 03 Mar, 2015 11:44 PM

    Yeah, this is happening on all the project types (Mvc, Web API, Web Forms, WinForms, WPF) when targeting .NET 4.5.. I just checked our old teamcity and I saw two of these warnings there too. Just odd because the warning says that ti's missing an SDK or targeting pack.

  24. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:54 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac

Recent Discussions