JonKazama-Hellion/HellionChat
1
0
Fork 0
Code Issues 1 Pull Requests Actions Releases 28 Activity

build: align RootNamespace with HellionChat post-rename

Browse Source 
Updates the project root namespace and replaces the historical comment
about cherry-pick compatibility — that compatibility was the rationale
for keeping ChatTwo.* in source while AssemblyName was already
HellionChat. With v1.0.0 the standalone cut is complete and both
identifiers match.

Note: this commit also fixes the runtime MissingManifestResourceException
that the previous Task 6 commit caused — the embedded resource prefix
is derived from RootNamespace at build time, so Designer.cs string
arguments and the actual resource names only line up once both are set
to HellionChat.
This commit is contained in:
Jon Kazama
2026-05-03 21:27:50 +02:00
parent 7d5496e959
commit cd6afb32cb
1 changed files with 5 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ChatTwo/ChatTwo.csproj
+5 -6
View File
@@ -6,13 +6,12 @@
derives from. --> derives from. -->
<Version>0.6.1</Version> <Version>0.6.1</Version>
<ImplicitUsings>enable</ImplicitUsings> <ImplicitUsings>enable</ImplicitUsings>
<!-- HellionChat fork: assembly is renamed so Dalamud uses <!-- v1.0.0 standalone cut — both AssemblyName and RootNamespace
pluginConfigs/HellionChat instead of pluginConfigs/ChatTwo, are HellionChat. The plugin no longer maintains source-level
keeping our state independent from the upstream plugin. cherry-pick compatibility with upstream Infiziert90/ChatTwo;
Code namespace stays ChatTwo.* so upstream cherry-picks upstream changes are integrated manually if at all. -->
apply cleanly. -->
<AssemblyName>HellionChat</AssemblyName> <AssemblyName>HellionChat</AssemblyName>
<RootNamespace>ChatTwo</RootNamespace> <RootNamespace>HellionChat</RootNamespace>
</PropertyGroup> </PropertyGroup>
<ItemGroup> <ItemGroup>