Results 1 to 8 of 8

Thread: [RESOLVED] Crossed References? Build Warnings

  1. #1

    Thread Starter
    New Member Erlkoenig's Avatar
    Join Date
    Mar 2024
    Posts
    13

    Resolved [RESOLVED] Crossed References? Build Warnings

    When I build my program I'm getting a warning message (below). I'm not sure if it's of concern or how to fix it:
    Code:
    1>Build succeeded.
    1>
    1>"F:\Development\Application\Code\Basic\22\ILiAD\ILiAD.vbproj" (Build;BuiltProjectOutputGroup;BuiltProjectOutputGroupDependencies;DebugSymbolsProjectOutputGroup;DebugSymbolsProjectOutputGroupDependencies;DocumentationProjectOutputGroup;DocumentationProjectOutputGroupDependencies;SatelliteDllsProjectOutputGroup;SatelliteDllsProjectOutputGroupDependencies;SGenFilesOutputGroup;SGenFilesOutputGroupDependencies target) (1) ->
    1>(ResolveAssemblyReferences target) -> 
    1>  D:\Applications\Microsoft\Visual Studio\2022\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2401,5): warning MSB3277: Found conflicts between different versions of "System.Windows.Forms" that could not be resolved.
    1>D:\Applications\Microsoft\Visual Studio\2022\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2401,5): warning MSB3277: There was a conflict between "System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" and "System.Windows.Forms, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089".
    1>D:\Applications\Microsoft\Visual Studio\2022\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2401,5): warning MSB3277:     "System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" was chosen because it was primary and "System.Windows.Forms, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" was not.
    1>D:\Applications\Microsoft\Visual Studio\2022\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2401,5): warning MSB3277:     References which depend on "System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" [C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.8.1\System.Windows.Forms.dll].
    1>D:\Applications\Microsoft\Visual Studio\2022\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2401,5): warning MSB3277:         C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.8.1\System.Windows.Forms.dll
    1>D:\Applications\Microsoft\Visual Studio\2022\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2401,5): warning MSB3277:           Project file item includes which caused reference "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.8.1\System.Windows.Forms.dll".
    1>D:\Applications\Microsoft\Visual Studio\2022\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2401,5): warning MSB3277:             System.Windows.Forms
    1>D:\Applications\Microsoft\Visual Studio\2022\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2401,5): warning MSB3277:     References which depend on or have been unified to "System.Windows.Forms, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" [].
    1>D:\Applications\Microsoft\Visual Studio\2022\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2401,5): warning MSB3277:         D:\Applications\Nevron\OpenVision CE\Bin\Net80\Nevron.Nov.Host.WinForm.dll
    1>D:\Applications\Microsoft\Visual Studio\2022\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2401,5): warning MSB3277:           Project file item includes which caused reference "D:\Applications\Nevron\OpenVision CE\Bin\Net80\Nevron.Nov.Host.WinForm.dll".
    1>D:\Applications\Microsoft\Visual Studio\2022\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2401,5): warning MSB3277:             Nevron.Nov.Host.WinForm, Version=24.6.5.12, Culture=neutral, PublicKeyToken=b33b1a04bb5ca8ad, processorArchitecture=MSIL
    1>D:\Applications\Microsoft\Visual Studio\2022\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2401,5): warning MSB3277:             Nevron.Nov.WinFormControls, Version=24.6.5.12, Culture=neutral, PublicKeyToken=b33b1a04bb5ca8ad, processorArchitecture=MSIL
    1>D:\Applications\Microsoft\Visual Studio\2022\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2401,5): warning MSB3277:         C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Nevron.Presentation\v4.0_24.2.19.12__6656c5d1103e75cc\Nevron.Presentation.dll
    1>D:\Applications\Microsoft\Visual Studio\2022\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2401,5): warning MSB3277:           Project file item includes which caused reference "C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Nevron.Presentation\v4.0_24.2.19.12__6656c5d1103e75cc\Nevron.Presentation.dll".
    1>D:\Applications\Microsoft\Visual Studio\2022\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2401,5): warning MSB3277:             Nevron.Presentation, Version=24.2.19.12, Culture=neutral, PublicKeyToken=6656c5d1103e75cc
    1>D:\Applications\Microsoft\Visual Studio\2022\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2401,5): warning MSB3277:         C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Nevron.System\v4.0_24.2.19.12__6a987feae5e496fd\Nevron.System.dll
    1>D:\Applications\Microsoft\Visual Studio\2022\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2401,5): warning MSB3277:           Project file item includes which caused reference "C:\WINDOWS\Microsoft.Net\assembly\GAC_MSIL\Nevron.System\v4.0_24.2.19.12__6a987feae5e496fd\Nevron.System.dll".
    1>D:\Applications\Microsoft\Visual Studio\2022\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2401,5): warning MSB3277:             Nevron.System, Version=24.2.19.12, Culture=neutral, PublicKeyToken=6a987feae5e496fd
    1>D:\Applications\Microsoft\Visual Studio\2022\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets(2401,5): warning MSB3277:             Nevron.Presentation, Version=24.2.19.12, Culture=neutral, PublicKeyToken=6656c5d1103e75cc
    1>
    1>    1 Warning(s)
    1>    0 Error(s)
    1>
    1>Time Elapsed 00:00:08.78
    ========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
    ========== Build completed at 08:30 and took 08.877 seconds ==========
    Please note: This is a snip of just the summary...

    It's been there for a bit, and panicked when I read some posts about the code (MSB3277). I thought back and remembered about some of the adds/removes that happened as I was putting the program together and changing things around. That got me thinking and led me to create a new instance of the program and transferred the sources to it. However, I don't think that changed anything.

    I have a more verbose dump of the build log (set output to DETAILED for it), but I can't make heads or tails of a lot of it. If someone wants to look at it, I can post the entire thing...

    What do I need to modify in order to fix the issues raised by the warning?
    Last edited by Erlkoenig; Jun 21st, 2024 at 11:08 AM.

  2. #2
    PowerPoster techgnome's Avatar
    Join Date
    May 2002
    Posts
    34,604

    Re: Crossed References? Build Warnings

    You've got somethings that are .NET FW 4.0 ... and something that's referencing (or built in) .NET CORE 8.0 ... they're not compatible with each other... One is WinForms based (4.0) and the other is Core based (8.0) ... Pick one or the other.


    -tg
    * I don't respond to private (PM) requests for help. It's not conducive to the general learning of others.*
    * I also don't respond to friend requests. Save a few bits and don't bother. I'll just end up rejecting anyways.*
    * How to get EFFECTIVE help: The Hitchhiker's Guide to Getting Help at VBF - Removing eels from your hovercraft *
    * How to Use Parameters * Create Disconnected ADO Recordset Clones * Set your VB6 ActiveX Compatibility * Get rid of those pesky VB Line Numbers * I swear I saved my data, where'd it run off to??? *

  3. #3

    Thread Starter
    New Member Erlkoenig's Avatar
    Join Date
    Mar 2024
    Posts
    13

    Re: Crossed References? Build Warnings

    Thank you. I cleared out all references, then turned around and re-added them. Not sure how the two got mixed up. On adding the Nevron references via "Browse", I found there are DLLs for Core60, Core70, Core80, Net20, and Net40. A bit of further digging made me check, and I found that Project/Application/Target FW is set to 4.8.1.

    I'm going to blame Micro$oft for this one: Their nomenclature is confusing (to me anyway). To me, "CORE" is equivalent to "Engine", making "NET" an environment (think NET40 under CORE80 being the most recent of both). But in overly simplified terms, CORE and NET are effectively synonymous and doing the same thing with different capabilities attached...

    Anyway, after that purge and reapply, the warnings are gone.

  4. #4
    PowerPoster techgnome's Avatar
    Join Date
    May 2002
    Posts
    34,604

    Re: [RESOLVED] Crossed References? Build Warnings

    Yeah.. the numbering and naming has left a lot to desire... there was .NET FW all the way through 4 something... somewhere they introduced .NET Core, which quickly got to 3... then it skipped 4, re-started at 5, then with 6, they decided to drop the CORE nomenclature since .NET Framework wasn't going to be moving forward any more... so .NET 7, then 8 came out.... but it shouldn't be surprising for a company that went XBox -> XBox 360 -> XBox One.... so... meh...



    -tg
    * I don't respond to private (PM) requests for help. It's not conducive to the general learning of others.*
    * I also don't respond to friend requests. Save a few bits and don't bother. I'll just end up rejecting anyways.*
    * How to get EFFECTIVE help: The Hitchhiker's Guide to Getting Help at VBF - Removing eels from your hovercraft *
    * How to Use Parameters * Create Disconnected ADO Recordset Clones * Set your VB6 ActiveX Compatibility * Get rid of those pesky VB Line Numbers * I swear I saved my data, where'd it run off to??? *

  5. #5
    Super Moderator jmcilhinney's Avatar
    Join Date
    May 2005
    Location
    Sydney, Australia
    Posts
    110,587

    Re: [RESOLVED] Crossed References? Build Warnings

    Quote Originally Posted by techgnome View Post
    Yeah.. the numbering and naming has left a lot to desire... there was .NET FW all the way through 4 something... somewhere they introduced .NET Core, which quickly got to 3... then it skipped 4, re-started at 5, then with 6, they decided to drop the CORE nomenclature since .NET Framework wasn't going to be moving forward any more... so .NET 7, then 8 came out.... but it shouldn't be surprising for a company that went XBox -> XBox 360 -> XBox One.... so... meh... -tg
    .NET Framework started at 1.0 and went to 4.8.1. .NET Core started along the way and went from 1.0 t 3.1. They then "merged" .NET Framework and .NET Core and the result was .NET 5. .NET 5 was based on the .NET Core codebase but added features and functionality from .NET Framework. Because .NET was replacing .NET Framework and .NET Core, they went to the next version number based on the higher of those two versions. There was no .NET Core 4 or 5 or later.

  6. #6

    Thread Starter
    New Member Erlkoenig's Avatar
    Join Date
    Mar 2024
    Posts
    13

    Re: [RESOLVED] Crossed References? Build Warnings

    Quote Originally Posted by techgnome View Post
    Yeah.. the numbering and naming has left a lot to desire... there was .NET FW all the way through 4 something... somewhere they introduced .NET Core, which quickly got to 3... then it skipped 4, re-started at 5, then with 6, they decided to drop the CORE nomenclature since .NET Framework wasn't going to be moving forward any more... so .NET 7, then 8 came out.... but it shouldn't be surprising for a company that went XBox -> XBox 360 -> XBox One.... so... meh...
    Quote Originally Posted by jmcilhinney View Post
    .NET Framework started at 1.0 and went to 4.8.1. .NET Core started along the way and went from 1.0 t 3.1. They then "merged" .NET Framework and .NET Core and the result was .NET 5. .NET 5 was based on the .NET Core codebase but added features and functionality from .NET Framework. Because .NET was replacing .NET Framework and .NET Core, they went to the next version number based on the higher of those two versions. There was no .NET Core 4 or 5 or later.
    I'm not surprised, and frankly M$ should know better than that.

    If you pick a scheme, stick with the scheme. If you change things around enough, change names entirely and start fresh. For example: They could have given the conjoined system a sensible universal name like Common Objects (CO). Developers would use Common Objects Environment Developer (CO-ED) and end users would install Common Object Application Library (CO-AL) as the Runtime... Not only is that catchy, but it also injects a bit of humor into it.

    The back-and-forth nonsense we're living with causes nothing but trouble... LOL

  7. #7
    Super Moderator jmcilhinney's Avatar
    Join Date
    May 2005
    Location
    Sydney, Australia
    Posts
    110,587

    Re: [RESOLVED] Crossed References? Build Warnings

    Quote Originally Posted by Erlkoenig View Post
    I'm not surprised, and frankly M$ should know better than that.

    If you pick a scheme, stick with the scheme. If you change things around enough, change names entirely and start fresh. For example: They could have given the conjoined system a sensible universal name like Common Objects (CO). Developers would use Common Objects Environment Developer (CO-ED) and end users would install Common Object Application Library (CO-AL) as the Runtime... Not only is that catchy, but it also injects a bit of humor into it.

    The back-and-forth nonsense we're living with causes nothing but trouble... LOL
    Oh yeah, they should abandon the .NET name that they've spent decades marketing. Why would they drop that name when it is still the same platform? We'd then spend our time explaining to people the similarity between Common Objects and .NET instead of the difference between .NET Framework and .NET Core. You're just solving one problem and creating another, possibily bigger, problem.

  8. #8

    Thread Starter
    New Member Erlkoenig's Avatar
    Join Date
    Mar 2024
    Posts
    13

    Re: [RESOLVED] Crossed References? Build Warnings

    Quote Originally Posted by jmcilhinney View Post
    Oh yeah, they should abandon the .NET name that they've spent decades marketing. Why would they drop that name when it is still the same platform? We'd then spend our time explaining to people the similarity between Common Objects and .NET instead of the difference between .NET Framework and .NET Core. You're just solving one problem and creating another, possibily bigger, problem.
    Aside from trying for silliness (Developers work with COEDs and users get COAL), it wouldn't be the first time M$ did just that, the gist was that it's a good way to start fresh without those crazy, confusing jumps. And to be fair, Apple and Google are no different with the naming bit...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width