C# - Writing own class libraries

แชร์
ฝัง
  • เผยแพร่เมื่อ 8 ก.พ. 2025
  • If you want to support this channel, here's a link to my GitHub Sponsors profile: github.com/spo...
    In C# we use class libraries all the time! But how about writing own class libraries? In this video we'll build a class library, create a NuGet package from it and import the class library in another application.
    Related videos:
    Bubble sort: • C# - Bubble sort algor...
    Insertion sort: • C# - Insertion sort
    Selection sort: • C# - Selection sort
    Performance: • Performance comparison...

ความคิดเห็น • 15

  • @kopilkaiser8991
    @kopilkaiser8991 5 หลายเดือนก่อน

    Great tutorial. Thank you brother for all your efforts❤🎉

  • @radovanholcik6010
    @radovanholcik6010 3 ปีที่แล้ว +3

    Awesome and fast tutorial. Great explaining and no useless information. Helped a lot

  • @manjeetnandal1
    @manjeetnandal1 5 ปีที่แล้ว +1

    Great sharing!
    Many useful!
    Many thanks!

  • @niphomahlangu2733
    @niphomahlangu2733 3 ปีที่แล้ว

    This was helpful. Thanks a million. 🔥

  • @gordonkimmacaraeg1232
    @gordonkimmacaraeg1232 5 ปีที่แล้ว +2

    thank you for this

  • @engrqamarabbas9753
    @engrqamarabbas9753 5 ปีที่แล้ว

    Thanks a lot for the great lecture.

  • @thesecondantagoniser4008
    @thesecondantagoniser4008 2 ปีที่แล้ว

    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?

    • @Codewrinkles
      @Codewrinkles  2 ปีที่แล้ว +1

      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 :)

  • @BlueKaiTheEnd-
    @BlueKaiTheEnd- ปีที่แล้ว

    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.

    • @Codewrinkles
      @Codewrinkles  ปีที่แล้ว +1

      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.

  • @CurtisJensenGames
    @CurtisJensenGames 3 ปีที่แล้ว

    Now I just need permission to push to my company's library

  • @sourandbitter3062
    @sourandbitter3062 5 ปีที่แล้ว

    The minute + 40 seconds intro wasn't necessary.

    • @mycodelines
      @mycodelines 4 ปีที่แล้ว +7

      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.

    • @OnlyGamerNerd
      @OnlyGamerNerd 4 ปีที่แล้ว +2

      Why do you care. He did great!