Closed GoogleCodeExporter closed 9 years ago
That is because the Client Profile is a trimmed down version of the .Net
framework.
It is specifically designed to be _small_. However, to make it small, something
has
got to go. If SlimDX relies on anything that was trimmed, then what would
happen
when you load an run you application?
My guess is that SlimDX requires the full .Net Framework. Other than a little
saved
space, why not install the full framework anyway? Perhaps to build network
downloadable games, the consumer might not have to download the full framework.
But
with todays disk sizes and current we access speeds, is this really still an
issue?
Original comment by Crystal_...@hotmail.com
on 15 Jan 2009 at 8:45
Yes, the Client Profile is a trimmed-down version of the .Net framework, but it
cuts
mostly server-related libraries. I do not know of any reason why SlimDX would
need
any of those advances libraries. If for some reason it *does*, then fine, but I
haven't heard anyone actually confirm that and explain what, in particular,
SlimDX
requires.
The Client Profile is highly preferable for the substantial subset of users who
have
a setup that qualifies for the Client Profile. It is only a couple dozen megs,
while
the full framework can be upwards of a couple hundred -- even on my high-speed
connection, that can take an annoying amount of time, especially if I'm at a LAN
party or something similar and I want to get the game installed quickly. And
even in
this day and age, some users *still* have dialup, not to mention other parts of
the
world that lack the broadband penetration of the 1st-world.
Original comment by holyfuzz...@gmail.com
on 15 Jan 2009 at 1:14
The fact that SlimDX will not install on a computer with only the Client
Profile
installed should imply that there is something else that SlimDX is using that
is
needed.
Also note that this only affect Windows XP. Vista forward has the .Net
Framework
installed by default. I wonder what support for this Client Profile will be
going
forward?
Original comment by Crystal_...@hotmail.com
on 15 Jan 2009 at 3:52
This may just be a bug in the installer in detecting what version(s) of the
.NET
Framework are currently installed. I don't KNOW if SlimDX runs on this profile
or
not. I will try and do some virtual machine tests prior to the March release to
see
if this can be straightened out.
Original comment by promit....@gmail.com
on 18 Jan 2009 at 2:51
Tagging for March.
Original comment by Mike.Popoloski
on 18 Feb 2009 at 8:36
I am unable to repro in XP. I created an XP SP3 setup, and installed this:
http://www.microsoft.com/downloads/details.aspx?FamilyId=8CEA6CD1-15BC-4664-B27D
-
8CEBA808B28B&displaylang=en
SlimDX installs and runs afterwards. I will try Vista but I see no reason it
would
fail there...
Original comment by promit....@gmail.com
on 12 Mar 2009 at 1:03
So, SlimDX November will install on a completely untouched out of the box Vista
install. I dunno what to tell you...no repro.
Original comment by promit....@gmail.com
on 12 Mar 2009 at 1:32
Hmm...
The client profile will only be installed on WinXP machines with *NO* .Net
Framework
already installed. On Vista or if any version of .Net is already installed, the
client profile installer will actually install the full .Net 3.5. See the chart
in
section 1.2 of:
http://download.microsoft.com/download/5/a/a/5aa86d6c-969b-42d8-bc6b-30e02bfeccf
0/NETFXClientProfile_DeploymentGuide.htm
Is it possible that the WinXP machine you tested on had some version of .Net
already
installed?
I will test again when I have some time. Thanks.
Original comment by holyfuzz...@gmail.com
on 12 Mar 2009 at 2:00
Hate to resurrect an old issue... but I finally got around to testing again and
have
been able to repro the issue.
My test platform is a clean install of WinXP SP3 on MS Virtual PC. I installed
the
Client Profile using the installer found at the following link:
http://www.microsoft.com/downloads/details.aspx?FamilyId=8CEA6CD1-15BC-4664-B27D
-8CEBA808B28B&displaylang=en
Then I attempted to install SlimDX. Attached is a screenshot showing that the
client
profile is indeed installed (and I can confirm by running an application
compiled for
it) along with the error message generated by the SlimDX installer.
This is by no means a show-stopping issue, though it would be nice because a
lot of
my users run WinXP w/o .Net installed and it takes quite a long time to
download and
install the full version. But again, don't kill yourself over this one. ;-)
Just FYI, I'm not sure how you check for the existence of the full .Net
framework in
the installer, but to check specifically for the client profile, you can check
for
the existence of this registry path:
HKLM\SOFTWARE\Microsoft\NET Framework Setup\DotNetClient\v3.5
Thanks for all the hard work!
Original comment by holyfuzz...@gmail.com
on 24 Jun 2009 at 1:19
I think I forgot to attach the screenshot...
Original comment by holyfuzz...@gmail.com
on 24 Jun 2009 at 1:21
Attachments:
I think I found the problem...
Looking in Redist.wxs, it looks like these lines check for the .Net framework:
<Condition Message="This application requires .NET Framework 2.0 or later. Please
install the .NET Framework then run this installer again.">
<![CDATA[Installed OR NETFRAMEWORK20 OR NETFRAMEWORK35]]>
</Condition>
According to http://wix.sourceforge.net/manual-wix3/wixnetfxextension.htm it
looks
like you should simply be able to add add a NETFRAMEWORK35_CLIENT condition to
those
above.
I'm not familiar with WiX, nor do I have the proper tools installed to compile
it
myself, so I haven't tested this.
Original comment by holyfuzz...@gmail.com
on 24 Jun 2009 at 2:10
Re-opening for testing.
Original comment by promit....@gmail.com
on 24 Jun 2009 at 2:46
I agree with you that the problem is just the check for the .NET framework
version,
but of course I have to go through the whole VM song and dance, along with an
installer build, to make sure. Le sigh.
Original comment by promit....@gmail.com
on 24 Jun 2009 at 2:51
If I send you a testing installer build in the next day or two, can you check
to see
if it works?
Original comment by promit....@gmail.com
on 6 Jul 2009 at 7:50
"If I send you a testing installer build in the next day or two, can you check
to see
if it works?"
- Of course!
Original comment by holyfuzz...@gmail.com
on 6 Jul 2009 at 7:53
Okay, this is a straight repack of the March redist with the new attribute
added in.
(NOT current code.) Let me know what happens.
Original comment by promit....@gmail.com
on 6 Jul 2009 at 9:34
Surprisingly it still does not work. Exact same error message.
Perhaps you need the NETFRAMEWORK35_CLIENT_SP_LEVEL flag as well? (Probably
not, but
I don't have any other ideas.)
Original comment by holyfuzz...@gmail.com
on 6 Jul 2009 at 9:50
Okay, let's try this again. I think I missed an important line before.
Original comment by promit....@gmail.com
on 7 Jul 2009 at 2:52
Attachments:
It works! Thanks so much. This will make installing my game a much faster
experience
for many users.
(This installer is simply the March 09 release repackaged, correct?)
Original comment by holyfuzz...@gmail.com
on 7 Jul 2009 at 2:59
Right, that's a straight repack of the Mar09 tag, with SP1 patches. Good thing
I tag
all the releases.
Original comment by promit....@gmail.com
on 7 Jul 2009 at 3:22
Original issue reported on code.google.com by
holyfuzz...@gmail.com
on 7 Dec 2008 at 7:41