Continuous Deployment to Linux - A TimCo Retail Manager Video

[@FATPENGUIN96]

[25:56] Just a presentation tip, use the Magnifier ['Windows' and '+'] keys at the same time, instead of Zooming in. Zooming in messes up the layout with responsive designs. I changed the zoom level to 200% and set the view to Lens. Then as soon as you load the magnifier it's already setup and follows where your mouse pointer is. When you are all done, ['Windows' and 'ESC'] keys at the same time to close. Loving the videos as always, keep up the good work.

[@IAmTimCorey]

Thanks for the tip.

[@andresbeltran5779]

Im so happy tim, this part about azure and deployment was excellent. Creat job

[@IAmTimCorey]

Thank you!

[@eanasthaichi99]

Thanks Tim for all your great videos. Till last video it worked fine. But now its showing application error when i run Api url. When diagnosed resource it showed container issue, your app started but did not respond to health checks

[@WeistDuDochNet]

If someone gets an Error like this "##[error]Error: The process 'C:\Program Files\dotnet\dotnet.exe' failed with exit code 1" dont search for an hour like me, just check your spacing in the dotnet publish Arguments (no space between linux and -x64) @IAmTimCorey keep up the work, helping so much to follow this series

[@IAmTimCorey]

Thanks for sharing. Im glad you are getting value out of my content.

[@saurabhchauhan232]

Liked video before watching, that my confidence on your tutorial sir, thank you very much for all the videos

[@IAmTimCorey]

Thank you!

[@darrensmith7949]

Hi, I thought in way of a thank you to Tim, and also just to help that I would share from my experience last few videos on pipelines, as at the end of this video Tim mentions restrictions being made by Azure which seem to be different / ongoing in 2021. Azure at time of writing March 2021 seems to also be restricting pipelines and jobs stayed queued forever on free tier. Drilling down into job I received the following message in logs "This agent request is not running because you have reached the maximum numberFinally after no reply and really wanting to carry on in the videos without skipping I needed to try something different, and was a little nervous of the Azure billing options :-) I chose to try a "local Self Hosted agent" instead meaning my laptop would do the work orchestrated by Azure DevOps. Including research and a bit of trial and error was running smoothly inside 15 minutes. As a hint - in Pipeline - Agent Pool - Manage - I created one called SelfHosted and used that instead of the AzurePipelines option. I downloaded the package to my local machine, and followed instructions to extract and configure using powershell ( also had to create a PAT / Token in Azure) During config you can run as a service or in powershell ( which I chose latter). Not quite full cloud, but free and no queueing, and works well for both CI/CD, and I could continue with the videos maybe a little slower on the first runs. Hope it helps. @Tim - Thanks again for really great course - looking forward to Bug fixing, and Blazor videos

[@IAmTimCorey]

I'm glad you got it working. There is a limit on the number of minutes on the free tier, I believe, so that might be what you were running into. I'm glad you got it working.

[@quentincouissinier8533]

Hi Tim and the team! Did you ever stumble upon a case where , after the deployment, the server content would be updated but not the view(s) of the application? After making changes to both Index.csthtml and _layout.cshtml I can't see any modification when launching the application. Made my research and found out about this cool Kudu tool though. So, I went to check my /Views folder on the server using it and all the updates could be found. So far, I tried: - Restarting the application. - Disabling caching. - Trying the application from an other computer. - Cleaning the solution, rebuilding it with minor changes and syncing it again. - Double checking the drop generated by the build would correspond to the latest modification. I ain't giving up, but feeling a little stuck in here. Thank you for your attention, and have a great day !

[@quentincouissinier8533]

My god. Feeling ridiculous haha. I usually stop the video when I face some bugs on my side and come back to it when I've found my solutions to follow along with you. The passage from "2019" to "2020" in the footer got me good. Little did I know the solution was few second ahead. Sorry for the comment and thanks again for the great work !

[@pilotboba]

Love to see moving from the UI based Build to the YAML configuration which allows you to work on the pipeline in a branch without modifying how master is building until you merge.

[@IAmTimCorey]

That is coming at some point. YAML is just so messy. I'll get there though, once I figure out how to make it easier.

[@pilotboba]

@@IAmTimCorey Got it. It seems like a lot of the pipelines doc not focuses on configuring builds with the YAML and not with the UI. Plan to convert, but haven't had time to myself. Even still, may have to move to gitlab... since that's what corporate uses and hosts.

[@kontrolla1]

Another great video Tim

[@IAmTimCorey]

Thanks!

[@theElectrASiAN]

I just learned Azure DevOps CI/CD through this TimCo series. Thanks. Just a doubt: why did you choose linux over windows for this application, in Azure App Service?

[@IAmTimCorey]

Just to do something different. Linux is also a cheaper host.

[@theElectrASiAN]

@@IAmTimCorey OK, got it.

[@dehaaneric]

Thanks Tim, this video (and the rest of the series) helped me a lot!

[@IAmTimCorey]

Great to hear!

[@suyashchandra5431]

If you could have did a little visualization part in the battleship project to make things clear about the grid it would been have so clear! I found it little confusing especially at displaying the shot grid part.

[@IAmTimCorey]

Thanks for the suggestion.

[@brainyexpert8221]

Great Videos, can you create comprehensive for this retail app , like using crystal report and many other good report module.

[@IAmTimCorey]

I will add it to the list. Thanks for the suggestion.

[@FunTime4KidsTV]

Good tutor, such wonderful series, please how can i add more scope by extending this project ? do i need to recreate everything in duplicate or how ? i want to add more scope, like additional model, table functionality.Thanks

[@IAmTimCorey]

You can definitely add more to this project without recreating everything. That is the point of this project. In the real world, you don't get the opportunity to start over very often. You have to take an existing application and add new features to it without making a mess. That last part is the trickiest to get right.

[@FunTime4KidsTV]

@@IAmTimCorey Yes sure its the trickiest to get, how i wish i could get a guide on how to extend the feature without making a mess of the entire project. Thanks

[@austinturney2060]

I keep getting an error "403 Forbidden" when using the pipeline to deploy the API, but not when I publish using Visual Studios. Has anyone found a solution?

[@LarryB15]

Just a heads up that the Create Release has had a major upgrade and the UI is broken into a number of graphical stages rather than a textual output.

[@IAmTimCorey]

That's what I have to, but if you click into the actual job, you can see the text output.

[@chaitanyapokuri900]

hi great videos i am having a query about deployment of .net application to iis server through linux with commands

[@tomthelestaff-iamtimcorey7597]

I think I have seen this topic addressed by viewers before. Can any of you Linux folks offer Chaitanya some help here?

[@LarryB15]

Really struggled with this. At the point you replaced the Build API step with the publish step my whole release pipeline started to fail. I could not get the DotNet publish to work at all.

[@IAmTimCorey]

Bummer. Time for some debugging. Keep at it. You can do it.

[@LarryB15]

@@IAmTimCorey It turns out that there was another project in the repository, which wasn't part of the solution and the DotNet publish command was trying to publish it. The strange thing was that all of the subsequent builds were skipped over too. Shouldn't it only try to publish projects actually in the solution?

[@sebastiandhom7172]

@@LarryB15 got that same error. I have unchecked the "publish web projects" and then typed "**/TRMApi/TRMApi.csproj" in that path textbox... Seems to work now.

[@mohamaddjelouah9332]

I love it thank u tim

[@IAmTimCorey]

You are welcome.

[@donhan5577]

After using dotnet publish (Build API Project disabled) with argument: -r linux-x64 --output $(build.artifactstagingdirectory), the dotnet publish failed. Error message is: C:\Program Files\dotnet\sdk\3.1.302\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.CrossTargeting.targets(27,5): error : The 'Publish' target is not supported without specifying a target framework. The current project targets multiple frameworks, please specify the framework for the published application. [d:\a\1\s\TRMDataManager.Library\TRMDataManager.Library.csproj] . What have I missed? Using Build API Project works before this change.

[@klauskunzli9441]

I replaced @DataTime.Now.Year by 2020. Now it works again.

[@klauskunzli9441]

@DateTime.Now.Year is correct

[@IAmTimCorey]

Not sure what issue you are having here but something seems to be configured incorrectly.

[@sergegoujon8022]

There's no link to full playlist in the description!

[@99MrX99]

kzbin.info/aero/PLLWMQd6PeGY0bEMxObA6dtYXuJOGfxSPx

[@IAmTimCorey]

Thanks for pointing it out. I updated the description.

[@davefrazier6019]

I've been following the video series this far without issue. I just setup the release pipeline as shown here. Azure Devops shows the release pipeline succeeded and I managed to find some logs on Azure for the web app that the deployment was successful. However, the API just shows a page with ":( Application Error" when I navigate to it. The application logs on Azure say "Cound not find build manifest file at '/home/site/wwwroot/oryx-manifest.toml'" and also later "It was not possible to find any installed .NET Core SDKs". It's possible that parameters and values used in this video are no longer valid. I'll go back and double check my settings. I'll post again here if/when I find a solution.

[@davefrazier6019]

release pipeline is working now. i actually replaced the build pipeline to get the release pipeline working as intended. I created a new single project build pipeline, but instead of using the asp.net template ... i used the ASP.NET Core build pipeline to start with [NOTE: not the "ASP.NET Core (.NET Framework)" template]. Interestingly, the new pipeline uses dotnet cli commands (does not appear to be using MSBuild directly but i could be mistaken) and the artifact that is created is just a zip file without the build.SourceLabel etc.). The zip file from the "dotnet build" has all of the a dll's-etc. in the root of the directory; as opposed to the MSBuild zip that had multiple nested directories with the application files at the bottom. I'm going to go back and tweak it to do the multi-project build or create individual build pipelines if need be. The build agent in the new pipeline is Ubuntu, but I'm pretty sure I'm going to need a .NET Framework environment for the SQL Database project.

[@davefrazier6019]

I owe you an apology. I just finished the video and realized the answer was there all along. I paused the video because I experienced the pipeline error earlier than you did. I think something changed in the Azure service since the time this video dropped. It seems like the Azure app service continued using the previous build of the app when you published it, but when I published it I got an application error right away. Since it appeared that my results were different I decided to stop watching until I could get it sorted. But now I see that if I had finished the video it would have saved me a bit of time. Although it was sort of cool because I ended up with similar solution even if it did take me a lot longer to get there. Thanks for all of the great content!

[@okmr.2073]

##[error]Error: C:\Program Files\dotnet\dotnet.exe failed with return code: 1 ##[error]Dotnet command failed with non-zero exit code on the following projects : D:\a\1\s\RMDataManager\RMDataManager.csproj if you meet these error messages, you should delete all files and folders of [RMDataManager project].

[@IAmTimCorey]

Thanks for sharing.