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
  1. Home
  2. The Lounge
  3. Discontinued Microsoft Tools/platforms

Discontinued Microsoft Tools/platforms

Scheduled Pinned Locked Moved The Lounge
questionsharepointsysadmintoolsworkspace
50 Posts 19 Posters 1 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.
  • J JimmyRopes

    Tomz_KV wrote:

    What is the next to discontinue? SharePoint, Entity Framework, Windows 8?

    All of the above. :~

    **_Once you lose your pride the rest is easy.

    I would agree with you but then we both would be wrong._**
    The report of my death was an exaggeration - Mark Twain Simply Elegant Designs JimmyRopes Designs
    I'm on-line therefore I am. JimmyRopes

    T Offline
    T Offline
    Tomz_KV
    wrote on last edited by
    #40

    Microsoft promotes SharePoint heavily. I did some serious development in it with InfoPath. Unfortunately, InfoPath is gone. Have not heard anything about the future of SharePoint.

    TOMZ_KV

    J 1 Reply Last reply
    0
    • T Tomz_KV

      Microsoft promotes SharePoint heavily. I did some serious development in it with InfoPath. Unfortunately, InfoPath is gone. Have not heard anything about the future of SharePoint.

      TOMZ_KV

      J Offline
      J Offline
      JimmyRopes
      wrote on last edited by
      #41

      Just joking. :-D SharePoint is a good platform but InfoPath left a lot to be desired, namely since it stored all attachments in the form there was a limit to the number/size of attachments that could be stored. Another problem came if you changed the form, all prior saved forms needed to be saved with the new prototype form. Additionally all workflows started with the previous forms were broken. It was never something to be used in production. You say it is gone now. Good riddance. X|

      **_Once you lose your pride the rest is easy.

      I would agree with you but then we both would be wrong._**
      The report of my death was an exaggeration - Mark Twain Simply Elegant Designs JimmyRopes Designs
      I'm on-line therefore I am. JimmyRopes

      T 1 Reply Last reply
      0
      • T Tomz_KV

        Unfortunately no. I googled it and followed a number of links but they led to nowhere.

        TOMZ_KV

        P Offline
        P Offline
        patbob
        wrote on last edited by
        #42

        Have you asked around to see if someone can give or sell you their old installation media for it? I probably used to have a copy at my old job I'd have just sent you, but its long gone now.

        We can program with only 1's, but if all you've got are zeros, you've got nothing.

        T 1 Reply Last reply
        0
        • P patbob

          Have you asked around to see if someone can give or sell you their old installation media for it? I probably used to have a copy at my old job I'd have just sent you, but its long gone now.

          We can program with only 1's, but if all you've got are zeros, you've got nothing.

          T Offline
          T Offline
          Tomz_KV
          wrote on last edited by
          #43

          I did but not extensively. Since I do not develop any new functionality but only do "fixes", I have been ok with using VS 2012. Thanks for your suggestions.

          TOMZ_KV

          1 Reply Last reply
          0
          • J JimmyRopes

            Just joking. :-D SharePoint is a good platform but InfoPath left a lot to be desired, namely since it stored all attachments in the form there was a limit to the number/size of attachments that could be stored. Another problem came if you changed the form, all prior saved forms needed to be saved with the new prototype form. Additionally all workflows started with the previous forms were broken. It was never something to be used in production. You say it is gone now. Good riddance. X|

            **_Once you lose your pride the rest is easy.

            I would agree with you but then we both would be wrong._**
            The report of my death was an exaggeration - Mark Twain Simply Elegant Designs JimmyRopes Designs
            I'm on-line therefore I am. JimmyRopes

            T Offline
            T Offline
            Tomz_KV
            wrote on last edited by
            #44

            Microsoft announced the termination of InfoPath in Jan. 2014: http://blogs.office.com/2014/01/31/update-on-infopath-and-sharepoint-forms/[^].

            TOMZ_KV

            J 1 Reply Last reply
            0
            • T Tomz_KV

              Microsoft announced the termination of InfoPath in Jan. 2014: http://blogs.office.com/2014/01/31/update-on-infopath-and-sharepoint-forms/[^].

              TOMZ_KV

              J Offline
              J Offline
              JimmyRopes
              wrote on last edited by
              #45

              Micro$oft realized InfoPath was broken and had to terminate them. X| It is interesting that they pulled the plug on InfoPath before they had a replacement in place. Let's see what they come up with next. :confused:

              **_Once you lose your pride the rest is easy.

              I would agree with you but then we both would be wrong._**
              The report of my death was an exaggeration - Mark Twain Simply Elegant Designs JimmyRopes Designs
              I'm on-line therefore I am. JimmyRopes

              1 Reply Last reply
              0
              • T Tomz_KV

                Colborne_Greg wrote:

                Entity Framework will be gone shortly

                Are you serious about EF? Version 6 was released not long ago and 7 is on the way.

                TOMZ_KV

                C Offline
                C Offline
                Colborne_Greg
                wrote on last edited by
                #46

                its a redundant system

                1 Reply Last reply
                0
                • T Tomz_KV

                  Microsoft discontinued a lot of development tools/platforms over the years. The one that has a big impact on our company is the Active Server Page. We still have a lot of "Pages" that need maintenance from time to time without the development environment - Visual InterDev. It is a pain. What is the next to discontinue? SharePoint, Entity Framework, Windows 8?

                  TOMZ_KV

                  C Offline
                  C Offline
                  CAReed
                  wrote on last edited by
                  #47

                  Just finally reading my email for last week... I'm just curious about this thread: Why are complaining about classic ASP after it had been replaced by ASP.NET twelve years ago? Still, it's still available for use. In fact, it should be available for the next eight years, as its current lifetime is based on the tenth anniversary of Windows 8.

                  Christopher Reed "The oxen are slow, but the earth is patient."

                  T 1 Reply Last reply
                  0
                  • C CAReed

                    Just finally reading my email for last week... I'm just curious about this thread: Why are complaining about classic ASP after it had been replaced by ASP.NET twelve years ago? Still, it's still available for use. In fact, it should be available for the next eight years, as its current lifetime is based on the tenth anniversary of Windows 8.

                    Christopher Reed "The oxen are slow, but the earth is patient."

                    T Offline
                    T Offline
                    Tomz_KV
                    wrote on last edited by
                    #48

                    I was not complaining but just stating the difficulty of maintaining it. asp.net is a nice replacement but Microsoft did not provide a way to upgrade asp to asp.net. Basically it is "discontinued".

                    TOMZ_KV

                    C 1 Reply Last reply
                    0
                    • T Tomz_KV

                      I was not complaining but just stating the difficulty of maintaining it. asp.net is a nice replacement but Microsoft did not provide a way to upgrade asp to asp.net. Basically it is "discontinued".

                      TOMZ_KV

                      C Offline
                      C Offline
                      CAReed
                      wrote on last edited by
                      #49

                      Actually, in the Page directive for a Web Form page, you can set the AspCompat attribute to true. This provides support for VB6 components within a Web Form. Essentially, you could add a Page directive to an ASP page with AspCompat set to true and your classic ASP runs through the ASP.NET engine once you change the file extension from .asp to .aspx. Granted, this doesn't help in switching over to ASP.NET, but it's a starting point for moving a classic ASP site to ASP.NET. Regardless, classic ASP has not been "discontinued". It is still a viable solution in its own right, at least for the next eight years. Now, if we're talking about discontinued platforms, let's talk about FoxPro....

                      Christopher Reed "The oxen are slow, but the earth is patient."

                      T 1 Reply Last reply
                      0
                      • C CAReed

                        Actually, in the Page directive for a Web Form page, you can set the AspCompat attribute to true. This provides support for VB6 components within a Web Form. Essentially, you could add a Page directive to an ASP page with AspCompat set to true and your classic ASP runs through the ASP.NET engine once you change the file extension from .asp to .aspx. Granted, this doesn't help in switching over to ASP.NET, but it's a starting point for moving a classic ASP site to ASP.NET. Regardless, classic ASP has not been "discontinued". It is still a viable solution in its own right, at least for the next eight years. Now, if we're talking about discontinued platforms, let's talk about FoxPro....

                        Christopher Reed "The oxen are slow, but the earth is patient."

                        T Offline
                        T Offline
                        Tomz_KV
                        wrote on last edited by
                        #50

                        Thanks for the great insight!

                        TOMZ_KV

                        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