Understand it builds on your side. Noticed IDE right-click on web csproj publish to folder gives me this error:
16:41:25:514 C:\Program Files\dotnet\sdk\9.0.304\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.ConflictResolution.targets(112,5): Error NETSDK1152: Found multiple publish output files with the same relative path: D:\Playware\Projects\SkinGoPrime2\source-final\Ldr.Prime.Main\modules\lms\src\Ldr.Prime.Lms.Web\Pages\_ViewImports.cshtml, D:\Playware\Projects\SkinGoPrime2\source-final\Ldr.Prime.Main\modules\common\src\Ldr.Prime.Common.Web\Pages\_ViewImports.cshtml.
16:41:25:527
Command line publish works fine with this command:
dotnet publish "Ldr.Prime.Main.Web.csproj" --configuration Release --output "D:\..\..\...\Testing\IIS-Server-Folder-Serving-WebApp" --no-restore --self-contained false
Local m/c level VS2022 F5 to start the web app works perfect.
The problem was on the server IIS-hosted web app:.
Looking into Azure DevOps script, we were checking the build error by building all sub modules first and finally the Main solution that had the web start-up project. When all builds are successful, for publishing, we took pre-built artifacts from bin/ and published with --no-build option which somehow created all embedded & content conflicts, hence when we removed -- no-build and left the publish to properly build and publish together in one-go, problem is solved now:
# Publish main web application only (avoiding module conflicts)
- task: DotNetCoreCLI@2
displayName: 'Final Build cum Publish Main Web Application for Deployment'
inputs:
command: 'publish'
projects: 'src/Ldr.Prime.Main.Web/Ldr.Prime.Main.Web.csproj'
arguments: '--configuration $(buildConfiguration) --output $(Build.ArtifactStagingDirectory)/publish --no-restore --self-contained false'
zipAfterPublish: true
modifyOutputPath: false
Now all good.
What's baffling me is IDE publish of web project has issues and when done via command line no issues?
full source code links to download has been emailed. pls look into it
but still getting 404, irrespective - any idea where it's failing, do u need full access to code and devOps script? Is there a way to check the routing?
[nachi] said:
Build failed in devOps pipeline, but now publish fails because multiple modules have Pages/_ViewImports.cshtml and they're conflicting during publish.
hence tried this variation:
<ItemGroup> <!-- Embed static assets --> <EmbeddedResource Include="Pages\**\*.css" /> <EmbeddedResource Include="Pages\**\*.js" /> <EmbeddedResource Include="Components\**\*.js" /> <EmbeddedResource Include="Components\**\*.css" /> <EmbeddedResource Include="wwwroot\**\*.*" /> <EmbeddedResource Include="Pages\**\*.cshtml" /> <!-- Explicitly mark for Razor compilation --> <RazorGenerate Include="Pages\**\*.cshtml" /> <Content Remove="Pages\**\*.css" /> <Content Remove="Pages\**\*.js" /> <Content Remove="Components\**\*.js" /> <Content Remove="Components\**\*.css" /> <Content Remove="wwwroot\**\*.*" /> </ItemGroup>build succeeds and verified the Compiled Razor Views Are in the DLL with
findstr /s /i "AspNetCore" Ldr.Prime.Lms.Web.dllNo compiled Razor view classes! I DON'T see any types like:
AspNetCoreGeneratedDocument.Pages_Lms_Index Pages_Lms_Index _Views_Pages_Lms_Indexstill kind of stuck
Build failed in devOps pipeline, but now publish fails because multiple modules have Pages/_ViewImports.cshtml and they're conflicting during publish.
hence tried this variation:
<ItemGroup>
<!-- Embed static assets -->
<EmbeddedResource Include="Pages\**\*.css" />
<EmbeddedResource Include="Pages\**\*.js" />
<EmbeddedResource Include="Components\**\*.js" />
<EmbeddedResource Include="Components\**\*.css" />
<EmbeddedResource Include="wwwroot\**\*.*" />
<EmbeddedResource Include="Pages\**\*.cshtml" />
<!-- Explicitly mark for Razor compilation -->
<RazorGenerate Include="Pages\**\*.cshtml" />
<Content Remove="Pages\**\*.css" />
<Content Remove="Pages\**\*.js" />
<Content Remove="Components\**\*.js" />
<Content Remove="Components\**\*.css" />
<Content Remove="wwwroot\**\*.*" />
</ItemGroup>
build succeeds and verified the Compiled Razor Views Are in the DLL with findstr /s /i "AspNetCore" Ldr.Prime.Lms.Web.dll
No compiled Razor view classes! I DON'T see any types like: AspNetCoreGeneratedDocument.Pages_Lms_Index Pages_Lms_Index _Views_Pages_Lms_Index
still kind of stuck
I've tried the AI-Bot suggested tips to no avail. Have shared the code download link via email.
Yes cli and abp suite are same versions. Installed non preview and latest stable which is 5.3.
Screenshot in google drive: https://drive.google.com/file/d/11o041AyebffZsMPaRa1vAd1QFJXK0FF1/view?usp=sharing