build(indicators): make Indicators.csproj build against current ATAS installs - #179
Open
AlbertoAmadorBelchistim wants to merge 2 commits into
Open
AlbertoAmadorBelchistim wants to merge 2 commits into
AlbertoAmadorBelchistim wants to merge 2 commits into
Conversation
…platform Indicators.csproj referenced DevExpress.Data.v25.2 unconditionally. Current ATAS builds ship newer DevExpress versions (the Alpha/Beta installs use v26.1), and their assemblies reference that version, so building the public project against them fails in the WPF markup compiler: error MC1000: Could not find assembly 'DevExpress.Data.v26.1, Version=26.1.3.0 ...' Select the newest DevExpress.Data found in ATAS_BASE (installers keep older versions next to the new one), falling back to v25.2. The value can still be forced with -p:DevExpressDataVersion=vXX.Y. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01474y4c64ouxmxfuvhhvqdn
…om dependencies Building Indicators.csproj against an ATAS install fails in GenerateDepsFile: error MSB4018: ... An item with the same key has already been added. Key: ATAS.Indicators.Technical ResolveAssemblyReferences walks OFT.Editors -> OFT.Platform.Core -> ATAS.Strategies and picks up the platform's own ATAS.Indicators.Technical.dll from ATAS_BASE, which has the same name as this project's output. Remove that dependency after reference resolution so it is neither written to the deps file nor copied over the freshly built assembly. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01474y4c64ouxmxfuvhhvqdn
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Title: build(indicators): make Indicators.csproj build against current ATAS installs
Building
Technical/Indicators.csprojagainst a current ATAS install (tested with Alpha 8.0.16) fails in two places:DevExpress.Data.v25.2unconditionally, but Alpha/Beta ship and reference v26.1:The first commit picks the newest
DevExpress.Datafound inATAS_BASE(installers keep older versions next to the new one), falls back to v25.2, and can be forced with-p:DevExpressDataVersion=vXX.Y.Reference resolution reaches the platform's own
ATAS.Indicators.Technical.dllthroughOFT.Editors → OFT.Platform.Core → ATAS.Strategies. That DLL has the same name as this project's output. The second commit removes it from the resolved dependencies, so it is neither written to the deps file nor copied over the built assembly.Configurations, platforms and
ATAS_BASEare unchanged. With both commits the project builds against Alpha 8.0.16 and ATAS X Alpha 8.0.16.