Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Part 2 - Add Monkey Dialog" - trying to build and run it as it -> "The project needs to be deployed before we can debug. Please enable Deploy in the Configuration Manager."" #2

Open
ShamilS opened this issue Sep 6, 2024 · 1 comment

Comments

@ShamilS
Copy link

ShamilS commented Sep 6, 2024

  • opened MonkeyFinderHybrid.sln in VS 2022

  • NuGet packages were restored automatically;

  • rebuilt was OK:

    Rebuild started at 0:04...
    1>------ Rebuild All started: Project: MonkeyFinderHybrid, Configuration: Debug Any CPU ------
    Restored S:\Learning\Blazor\blazor-hybrid-workshop-main\Part 2 - Add Monkey Dialog\MonkeyFinderHybrid\MonkeyFinderHybrid.csproj (in 825 ms).
    1>MonkeyFinderHybrid -> S:\Learning\Blazor\blazor-hybrid-workshop-main\Part 2 - Add Monkey Dialog\MonkeyFinderHybrid\bin\Debug\net8.0-ios\iossimulator-x64\MonkeyFinderHybrid.dll
    1>MonkeyFinderHybrid -> S:\Learning\Blazor\blazor-hybrid-workshop-main\Part 2 - Add Monkey Dialog\MonkeyFinderHybrid\bin\Debug\net8.0-maccatalyst\maccatalyst-x64\MonkeyFinderHybrid.dll
    1>MonkeyFinderHybrid -> S:\Learning\Blazor\blazor-hybrid-workshop-main\Part 2 - Add Monkey Dialog\MonkeyFinderHybrid\bin\Debug\net8.0-android\MonkeyFinderHybrid.dll
    1>MonkeyFinderHybrid -> S:\Learning\Blazor\blazor-hybrid-workshop-main\Part 2 - Add Monkey Dialog\MonkeyFinderHybrid\bin\Debug\net8.0-windows10.0.19041.0\win10-x64\MonkeyFinderHybrid.dll
    ========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ==========
    ========== Rebuild completed at 0:05 and took 43.527 seconds ==========

  • Debug -> Start without debugging:

TheProjectNeedsToDeployed

  • Right-click on project name, select Deploy -> output:

    Creating a new clean layout...
    Copying files: Total 43 mb to layout...
    DEP1000: Cannot copy file "C:\Users\admin.nuget\packages\microsoft.fluentui.aspnetcore.components\4.9.3\staticwebassets\Components\DesignSystemProvider\FluentDesignTheme.razor.js" to layout "S:\Learning\Blazor\blazor-hybrid-workshop-main\Part 2 - Add Monkey Dialog\MonkeyFinderHybrid\bin\Debug\net8.0-windows10.0.19041.0\win10-x64\AppX\wwwroot_content\Microsoft.FluentUI.AspNetCore.Components\Components\DesignSystemProvider\FluentDesignTheme.razor.js". DirectoryNotFoundException - Could not find a part of the path 'S:\Learning\Blazor\blazor-hybrid-workshop-main\Part 2 - Add Monkey Dialog\MonkeyFinderHybrid\bin\Debug\net8.0-windows10.0.19041.0\win10-x64\AppX\wwwroot_content\Microsoft.FluentUI.AspNetCore.Components\Components\DesignSystemProvider\FluentDesignTheme.razor.js'. [0x80070003]
    ========== Build: 0 succeeded, 0 failed, 1 up-to-date, 0 skipped ==========
    ========== Build completed at 0:17 and took 00.641 seconds ==========
    ========== Deploy: 1 succeeded, 0 failed, 0 skipped ==========
    ========== Deploy completed at 0:17 and took 00.641 seconds ==========

  • Tried again: Debug -> Start without debugging:

TheProjectNeedsToDeployed


Do you have an effective solution of the subject issue? Did you try to go through your tutorial "Part 2 - Add Monkey Dialog" source code on a fresh PC?

@ShamilS
Copy link
Author

ShamilS commented Sep 6, 2024

continued...

Target deployment folder S:\Learning\Blazor\blazor-hybrid-workshop-main\Part 2 - Add Monkey Dialog\MonkeyFinderHybrid\bin\Debug\net8.0-windows10.0.19041.0\win10-x64\AppX\wwwroot\_content\Microsoft.FluentUI.AspNetCore.Components\Components\DesignSystemProvider

exists. But is has blanks. Could these blanks be the source/cause of the subject issue? Let's check:

When the whole solution folder with all the files was moved to the S:\Learning\Blazor\Issue folder, NuGet packages restored, solution cleared, closed, rebuilt then the The project needs to be deployed... issue disappeared. So I can assume the subject issue was caused by the target deployment fullpath having blanks.

But when I have tried to run the project's first time the result program window was:

AnUnahndledErrorHasOccurred

After a few more tries I have got the positive result program window:

FinallyAllMonkyesAreHere

Still unclear why on first runs the result was an "Unhandled exception" (debug/trace mode didn't allow to catch the source of this error).

So the recommendations would be:

  • to change the naming of the tutorial chapters for them to not have blank (or hyphen/dash - '-' ?) chars;
  • to introduce unhandled errors handling code in the very first sample project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant