I don't know if it's company computer settings or me missing a step, but I get a yellow triangle symbol on dependencies each time I install. This is preventing me from using the namespace and calling the methods.
The yellow triangle means that there is somewhere a version mismatch between the library. it's actually very tricky to investigate that. You should take a look at each library and what other packages/libraries it depends on, including exact versions.
Very comprehensive. Thank you. I'm curious as to why one would even bother using .NET core though since standard works for all applications? Is .NET core more resource efficient?
First of all, this video is very old. Actually it's from the beginning of .NET Core when thing were a little bit more volatile. However, an answer to your question would be, from my opinion, that it depends what you are trying to achieve. If you want to build a library only for .NET Core applications, then creating a .NET Core class library might be the way to go, since .NET Standards includes a lot of additional classes that are specific for cross platform development. It comes down to size. True, this shouldn't really matter in most cases nowadays. However, with the unification of the .NET portofolio I think everything will be unified soon and this discussion will probably get out of date :)
![Kodak Black - Versatile 4 [Official Video]](http://i.ytimg.com/vi/VcP_1Ua__vY/mqdefault.jpg)
Awesome and fast tutorial. Great explaining and no useless information. Helped a lot
Great tutorial. Thank you brother for all your efforts❤🎉
I don't know if it's company computer settings or me missing a step, but I get a yellow triangle symbol on dependencies each time I install. This is preventing me from using the namespace and calling the methods.
The yellow triangle means that there is somewhere a version mismatch between the library. it's actually very tricky to investigate that. You should take a look at each library and what other packages/libraries it depends on, including exact versions.
Very comprehensive. Thank you.
I'm curious as to why one would even bother using .NET core though since standard works for all applications?
Is .NET core more resource efficient?
First of all, this video is very old. Actually it's from the beginning of .NET Core when thing were a little bit more volatile. However, an answer to your question would be, from my opinion, that it depends what you are trying to achieve. If you want to build a library only for .NET Core applications, then creating a .NET Core class library might be the way to go, since .NET Standards includes a lot of additional classes that are specific for cross platform development. It comes down to size. True, this shouldn't really matter in most cases nowadays. However, with the unification of the .NET portofolio I think everything will be unified soon and this discussion will probably get out of date :)
Great sharing!
Many useful!
Many thanks!
Now I just need permission to push to my company's library
thank you for this
This was helpful. Thanks a million. 🔥
Glad to hear it!
Thanks a lot for the great lecture.
The minute + 40 seconds intro wasn't necessary.
programmers puts many years experience in single video and makes a lot of effort to convey his knowledge to us. we should support them not criticise.
Why do you care. He did great!