Re: using a dll in c#?
@7
VS is very old, and by a company that used to be enterprise as fuck. Their entire business model until at least 2010 was "we get people to use our stuff, then make sure they can't ever leave". Don't believe me, google embrace, extend, extinguish. There is a reason a lot of older programmers don't trust them: we were around for when they were evil. There are literally parts of windows that are specifically designed to be hard for other OSes to implement. They actually got into a lot of legal trouble for this kind of thing, though in the end it turned into a slap on the wrist, but nonetheless they were the first really big tech company to be hit with a successful antitrust lawsuit, which honestly hasn't been done successfully since because the bar is really just that high.
Unfortunately for everyone involved, in that time, they integrated a *ton* into VS. They've got a thing called msbuild, and my friend who works at Microsoft on the VS team flat out says that even internally almost no one knows how it works. It's some gigantic XML files. Want to build xaml or uwp? Try using some msbuild dlls that only msbuild understands. Want to add a bunch of default references? Well, vs is more than happy to edit your msbuild file, so much so that most vs devs don't even know what msbuild is.
You've got to remember, until 2012 or so VS cost some ridiculous amount of money for even individuals, they decided to make it free because it was that or start losing devs to other platforms. But C# is *not* a language that was originally designed with a mindset of being open and all that, it was designed with a mindset of how do we make sure devs never, ever, ever leave.
But this is the tech stack you're opting into. If you want out of VS, either pick a different language or deal with it for at least the next 5 years. They are admittedly working on transitioning to more friendly/open source stuff, but .net core is only able to do console/server apps at the moment with no support for the Windows-specific desktop stuff in sight so you can't do anything that isn't running in the terminal with it, and as long as you keep trying to use csc you're going to just keep having more and more questions like this one, and god help you if you decide to try UWP or XAML, because we certainly won't be able to.
-- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
