Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor
  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. The Lounge
  3. Whyyyyyy???

Whyyyyyy???

Scheduled Pinned Locked Moved The Lounge
announcementvisual-studiowpfwcftesting
8 Posts 7 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    Mel Padden
    wrote on last edited by
    #1

    So it turns out if i reference an older version of NHibernate in my project with NuGet, it downloads the dll alright, but it puts an assembly binding directive in my web.config which makes the app try to load a later version, with the result that the app breaks when I try to run it. Took me an hour to spot the damn directives, I looked everywhere else for the problem, checked every project in the solution for the correct NHibernate version. Eventually found the problem by chance. Why in the name of GOD would they do this? It makes no sense at all ever to do that! Why must Microsoft suck so hard at most things they do? Why must they release so much crap and features I don't want without testing their goddam code? (throws keyboard out window, sets fire to passing pensioner) OK rant over. Just... grrr...

    One morning I shot an elephant in my pajamas. How he got in my pajamas, I don't know.

    F L Z M M 5 Replies Last reply
    0
    • M Mel Padden

      So it turns out if i reference an older version of NHibernate in my project with NuGet, it downloads the dll alright, but it puts an assembly binding directive in my web.config which makes the app try to load a later version, with the result that the app breaks when I try to run it. Took me an hour to spot the damn directives, I looked everywhere else for the problem, checked every project in the solution for the correct NHibernate version. Eventually found the problem by chance. Why in the name of GOD would they do this? It makes no sense at all ever to do that! Why must Microsoft suck so hard at most things they do? Why must they release so much crap and features I don't want without testing their goddam code? (throws keyboard out window, sets fire to passing pensioner) OK rant over. Just... grrr...

      One morning I shot an elephant in my pajamas. How he got in my pajamas, I don't know.

      F Offline
      F Offline
      F ES Sitecore
      wrote on last edited by
      #2

      If you use source control you can spot these things much easier, just compare the working version with the last-known-good.

      1 Reply Last reply
      0
      • M Mel Padden

        So it turns out if i reference an older version of NHibernate in my project with NuGet, it downloads the dll alright, but it puts an assembly binding directive in my web.config which makes the app try to load a later version, with the result that the app breaks when I try to run it. Took me an hour to spot the damn directives, I looked everywhere else for the problem, checked every project in the solution for the correct NHibernate version. Eventually found the problem by chance. Why in the name of GOD would they do this? It makes no sense at all ever to do that! Why must Microsoft suck so hard at most things they do? Why must they release so much crap and features I don't want without testing their goddam code? (throws keyboard out window, sets fire to passing pensioner) OK rant over. Just... grrr...

        One morning I shot an elephant in my pajamas. How he got in my pajamas, I don't know.

        L Offline
        L Offline
        Lost User
        wrote on last edited by
        #3

        Mel Padden wrote:

        Why must they [microsoft] release so much crap and features I don't want without testing their goddam code?

        microsoft was founded in 1975, and now you're asking that question?

        Installing Signature... Do not switch off your computer.

        1 Reply Last reply
        0
        • M Mel Padden

          So it turns out if i reference an older version of NHibernate in my project with NuGet, it downloads the dll alright, but it puts an assembly binding directive in my web.config which makes the app try to load a later version, with the result that the app breaks when I try to run it. Took me an hour to spot the damn directives, I looked everywhere else for the problem, checked every project in the solution for the correct NHibernate version. Eventually found the problem by chance. Why in the name of GOD would they do this? It makes no sense at all ever to do that! Why must Microsoft suck so hard at most things they do? Why must they release so much crap and features I don't want without testing their goddam code? (throws keyboard out window, sets fire to passing pensioner) OK rant over. Just... grrr...

          One morning I shot an elephant in my pajamas. How he got in my pajamas, I don't know.

          Z Offline
          Z Offline
          ZurdoDev
          wrote on last edited by
          #4

          Mel Padden wrote:

          Why must Microsoft suck so hard at most things they do? Why must they release so much crap and features I don't want without testing their goddam code?

          Until someone can do it better. I also wonder how often our customers curse out the products we create. Yet we expect near perfection from Microsoft.

          There are two kinds of people in the world: those who can extrapolate from incomplete data. There are only 10 types of people in the world, those who understand binary and those who don't.

          M D 2 Replies Last reply
          0
          • Z ZurdoDev

            Mel Padden wrote:

            Why must Microsoft suck so hard at most things they do? Why must they release so much crap and features I don't want without testing their goddam code?

            Until someone can do it better. I also wonder how often our customers curse out the products we create. Yet we expect near perfection from Microsoft.

            There are two kinds of people in the world: those who can extrapolate from incomplete data. There are only 10 types of people in the world, those who understand binary and those who don't.

            M Offline
            M Offline
            Mel Padden
            wrote on last edited by
            #5

            Fair comment. It's just very frustrating. When have to implement a kludge I at least have the good grace to let the users know what to expect.

            One morning I shot an elephant in my pajamas. How he got in my pajamas, I don't know.

            1 Reply Last reply
            0
            • Z ZurdoDev

              Mel Padden wrote:

              Why must Microsoft suck so hard at most things they do? Why must they release so much crap and features I don't want without testing their goddam code?

              Until someone can do it better. I also wonder how often our customers curse out the products we create. Yet we expect near perfection from Microsoft.

              There are two kinds of people in the world: those who can extrapolate from incomplete data. There are only 10 types of people in the world, those who understand binary and those who don't.

              D Offline
              D Offline
              dandy72
              wrote on last edited by
              #6

              Gimme MS's resources, and I think I'd be able to have near perfect software. Of course said software would be a lot less ambitious.

              1 Reply Last reply
              0
              • M Mel Padden

                So it turns out if i reference an older version of NHibernate in my project with NuGet, it downloads the dll alright, but it puts an assembly binding directive in my web.config which makes the app try to load a later version, with the result that the app breaks when I try to run it. Took me an hour to spot the damn directives, I looked everywhere else for the problem, checked every project in the solution for the correct NHibernate version. Eventually found the problem by chance. Why in the name of GOD would they do this? It makes no sense at all ever to do that! Why must Microsoft suck so hard at most things they do? Why must they release so much crap and features I don't want without testing their goddam code? (throws keyboard out window, sets fire to passing pensioner) OK rant over. Just... grrr...

                One morning I shot an elephant in my pajamas. How he got in my pajamas, I don't know.

                M Offline
                M Offline
                Marc Clifton
                wrote on last edited by
                #7

                Mel Padden wrote:

                in my project with NuGet

                NuGet. The spawn of the devil.

                Mel Padden wrote:

                Took me an hour to spot the damn directives,

                Been there, took me more than an hour. :)

                Latest Article - Class-less Coding - Minimalist C# and Why F# and Function Programming Has Some Advantages Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802

                1 Reply Last reply
                0
                • M Mel Padden

                  So it turns out if i reference an older version of NHibernate in my project with NuGet, it downloads the dll alright, but it puts an assembly binding directive in my web.config which makes the app try to load a later version, with the result that the app breaks when I try to run it. Took me an hour to spot the damn directives, I looked everywhere else for the problem, checked every project in the solution for the correct NHibernate version. Eventually found the problem by chance. Why in the name of GOD would they do this? It makes no sense at all ever to do that! Why must Microsoft suck so hard at most things they do? Why must they release so much crap and features I don't want without testing their goddam code? (throws keyboard out window, sets fire to passing pensioner) OK rant over. Just... grrr...

                  One morning I shot an elephant in my pajamas. How he got in my pajamas, I don't know.

                  M Offline
                  M Offline
                  Mycroft Holmes
                  wrote on last edited by
                  #8

                  Are you bitching at VS, nHibernate or Nuget, 2 of which are rather nasty. Does MS own nHibernate now?

                  Never underestimate the power of human stupidity RAH

                  1 Reply Last reply
                  0
                  Reply
                  • Reply as topic
                  Log in to reply
                  • Oldest to Newest
                  • Newest to Oldest
                  • Most Votes

                  • Login
                  • Don't have an account? Register
                  • Login or register to search.
                  • First post
                    Last post
                  0
                  • Categories
                  • Recent
                  • Tags
                  • Popular
                  • World
                  • Users
                  • Groups