Reply to comment

While we appreciate comments from our users, please follow our posting guidelines. Have you tried the Cyotek Forums for support from Cyotek and the community?

Styling with Markdown is supported

Original Comment

Gravatar

Johan Eriksson

# Reply

Hello, and thanks for great tips ! Just wanted to mention VS Code as a great tool not only for text/webdev. I started using it for some .NET Core WEB API projects and some Azure Functions and its really great. I especially like that the projects feels more slim (not .sln based) and are easily used by team members sitting on for example Mac. And this is from an old bloke who has been using Visual Studio on a daily basis since Visual Basic 6...

And no, stay away from monorepos ! They make devops pipelines (CI/CD) really messy. You will regret it. If you have shared libs use private nugets/artifacts :)

Gravatar

Richard Moss

# Reply

Johan,

Thanks for taking the time to comment. I haven't really used VS Code for true development yet as I was still happy using Visual Studio for .NET Core (and I don't really have a choice for our WinForms stuff!). I did use its debugging facilities for use with PHP which I didn't find great, but I can probably blame that on PHP!

I do need to hurry up and finish bits of the new blog, I added reply notifications to it, but as comment moderation is still currently handled by the "old" site which doesn't know anything about them, no replies get sent... I think perhaps I'll try using VS Code to do this piece of work and see what happens.

Thanks for the tip re the mono repository. Most of my private libraries are as NuGet packages now, my main issue is probably going to be image resources that are linked from outside the project directories. I'll have to try and devote some serious time to looking into this properly.

Thanks again for the comments and suggestions.

Regards;
Richard Moss