Closed ks1990cn closed 10 months ago
Hello, Tanmay! Are you posting to us your build errors from your Visual Studio of unknown solution, as for me?! Or what are you doing? If you would like to discuss latest released version, then how were we be able to release in case of build errors? Our CI-CD build for the release 21.0 is green: Build 2640
Yes I can see its green, I am not sure what the problem I am getting. My develop branch of fork is up todate and my pull is getting me this error.
Its running fine now for me too, just system restart, clean and build help me. Not sure why VS behave stupid.
Hello, Tanmay! Are you posting to us your build errors from your Visual Studio of unknown solution, as for me?! Or what are you doing? If you would like to discuss latest released version, then how were we be able to release in case of build errors? Our CI-CD build for the release 21.0 is green: Build 2640
Its Ocelot solution, you can see GIT below. I agree screenshot doesn't have opened error point. Sorry
Tanmay, Tanmay... 😉
Pay attention when you switch Git branches in VS you will have invalid builds of previous branch. In this case VS behavior is unpredicted! You can experience errors, warnings and etc...
I recommend you to reload solution in VS, and even clean solution, and rebuild once again. So, just use very useful VS command "Build -> Clean Solution" ⚠️
Good luck in Ocelot development! :wink:
Don't say next time that we have breaking changes, man! 😠 😡
Yeah I struggled, not sure why cleanup wasn't helping me, even VS restart too🤣. I know I faced most stupid thing but I felt issue & you were online.
Obviously no one can't merge breaking changes
Latest build breaking @raman-m @ggnaegi
Steps to Reproduce the Problem