Thanks for the link. That method did not seem to work on Windows Server 2016. I have found a solution that seems to work correctly, if not very efficiently, on Windows 10. Since I doubt that Windows Server machines will be called on very often to build pywin32, I am leaving the script with a little message telling the unfortunate user to install dotNET 3.5 manually.
Still I wonder what part of our build system requires something so obsolete. On Thu, Mar 14, 2019 at 1:55 PM Denis Akhiyarov <denis.akhiya...@gmail.com> wrote: > Have you looked at this? > https://stackoverflow.com/questions/23631675/install-net-3-5-framework-on-windows-server-2012-without-dvd > > On Thu, Mar 14, 2019 at 1:29 PM Vernon D. Cole <vernondc...@gmail.com> > wrote: > >> I am trying to build a build machine (actually a script to build build >> machines) capable of creating a pywin32 distribution. (I need to test the >> distribution I am trying to fix.) >> >> Somewhere in there it seems that I need to have .net3.5 installed. I have >> been struggling with this all morning, and have come to the conclusion that >> I cannot install it on a Windows server operating system without having the >> distribution media mounted on a CD drive. >> >> That seems like a bad idea. >> >> Is the package actually needed for some reason? >> -- >> Vernon Cole >> >> _______________________________________________ >> python-win32 mailing list >> python-win32@python.org >> https://mail.python.org/mailman/listinfo/python-win32 >> >
_______________________________________________ python-win32 mailing list python-win32@python.org https://mail.python.org/mailman/listinfo/python-win32
