search

Claudio6969 / slimdx

Automatically exported from code.google.com/p/slimdx
MIT License
0 stars 1 forks source link

Slimdx Runtime for .Net 4.0 (March 2011) can't be installed on .NET 4.0 Client Profile installed PC #790

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
I have tried to install Slimdx Runtime for .Net 4.0 (March 2011) on Windows 7 
x86 Home Premium laptop with .Net 4.0 Client Profile installed.But it has failed

Original issue reported on code.google.com by onuracen...@gmail.com on 14 Apr 2011 at 12:15

GoogleCodeExporter commented 8 years ago 
It's a known issue (listed in the SDK), unfortunately there wasn't time to fix 
it before the release. For the time being, you will need the extended .NET 4 
runtime installed. Hopefully that requirement will not last too much longer.

Original comment by promit....@gmail.com on 14 Apr 2011 at 2:28

GoogleCodeExporter commented 8 years ago 
not client but full version of .NET 4 you mean? (dev+client)

Original comment by onuracen...@gmail.com on 14 Apr 2011 at 3:00

GoogleCodeExporter commented 8 years ago 
The version that this installs:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=9cfb2d51-5ff4-4491-b
0e5-b386f32c0992&displaylang=en
It shows up in the Programs (uninstall) list as Microsoft .NET Framework 4 
Extended. It's not a developer package.

Original comment by promit....@gmail.com on 14 Apr 2011 at 4:39

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
No. You misunderstand the meaning of "Client Profile". None of the 
redistributables are "developer" packages. That's why they're redistributables 
and not SDKs.

Original comment by Mike.Popoloski on 14 Apr 2011 at 5:32

GoogleCodeExporter commented 8 years ago 
combined version you mean. in other words full version which includes dev and 
client packs which I referred in my previous comment.
but without this requirement I have successfully installed slimdx in another 
pc. the only difference was the OS.it was win7 pro

Original comment by onuracen...@gmail.com on 14 Apr 2011 at 5:33

GoogleCodeExporter commented 8 years ago 
The Client Profile is used to run most client applications that target the .NET 
Framework 4
.NET Framework 4 is required to run and "develop" applications to target the 
.NET Framework 4

those descriptions stated by Microsoft. it is possible that I misunderstand 
that.

Original comment by onuracen...@gmail.com on 14 Apr 2011 at 5:38

GoogleCodeExporter commented 8 years ago 
Anyway. a normal user is not aware of this as they started to use windows 7. 
and as the build-in version is client, slimdx setup should be fixed according 
to this version.

Original comment by onuracen...@gmail.com on 14 Apr 2011 at 5:45

GoogleCodeExporter commented 8 years ago 
Yes. You have misunderstood. They are not developer packages, except in the 
sense that you obviously can't develop applications without the runtimes 
installed.

The extended framework installer is analogous to the .NET 2 installer, since 
.NET 2 didn't have a Client Profile version. It's an optimization, and one want 
to make eventually, but it's in no way a show stopper or even really a bug.

Original comment by Mike.Popoloski on 14 Apr 2011 at 5:50

GoogleCodeExporter commented 8 years ago 
so,there should be a link to .Net 4 before installing slimdx (.net 4 version) ?

Original comment by onuracen...@gmail.com on 14 Apr 2011 at 5:55

GoogleCodeExporter commented 8 years ago 
Yes, if you want to deploy .NET 4 applications, the target machine must have 
.NET 4 installed. You can either link to the web installer or include the full 
redistributable embedded in your own application's installer.

The SlimDX installers do not bundle the .NET runtimes because they are large 
and most people have them installed already.

Original comment by Mike.Popoloski on 14 Apr 2011 at 5:58

GoogleCodeExporter commented 8 years ago 
no,I meant pointing .net 4 full version page link in slimdx download page

Original comment by onuracen...@gmail.com on 14 Apr 2011 at 6:03

GoogleCodeExporter commented 8 years ago 
Setting milestone.

Original comment by Mike.Popoloski on 27 Jul 2011 at 1:42

GoogleCodeExporter commented 8 years ago 
This problem has been fixed for the upcoming Aug 11 release.

Original comment by promit....@gmail.com on 21 Aug 2011 at 12:09

GoogleCodeExporter commented 8 years ago

Original comment by promit....@gmail.com on 21 Aug 2011 at 12:10

GoogleCodeExporter commented 8 years ago 
I'm assuming this fix is available in the Sept 2011 release, but the download 
page still says "The 4.0 runtime is not available yet, but will be released in 
a few days."  I was going to just use the March 2011 release, but it does not 
support the .NET 4 Client Profile, which I need.

Any idea when we'll see the .NET 4 version of the Sept 2011 release (with 
support for .NET 4 Client Profile)?

thanks!

Original comment by j...@lyonscastle.com on 10 Nov 2011 at 12:09

GoogleCodeExporter commented 8 years ago 
Still waiting for the September 2011 redist for .NET 4.0.
A "few days" have gone by quickly... ;-)

Original comment by antao.al...@gmail.com on 5 Dec 2011 at 5:58

GoogleCodeExporter commented 8 years ago 
Thanks a lot for making available a .NET 4.0 runtime.
Unfortunately, I've just installed "SlimDX Runtime .NET 4.0 x86 (January 2012)" 
and checked the target profile of the SlimDX assembly (using ILSpy) and it's 
still not the client profile... :(
The .NET 4.0 Client Profile is installed by the Windows Update while the full 
profile requires the user to run an installer that includes stuff targeted for 
servers and developer machines.
More info on the client profile at 
http://msdn.microsoft.com/en-us/library/cc656912.aspx
Thanks,
aalmada

Original comment by antao.al...@gmail.com on 30 Jan 2012 at 10:42

GoogleCodeExporter commented 8 years ago 
Yeah, did not know that it needs to be set on the assembly itself. VC helpfully 
fails to expose it as a setting as well. I've attached a new test binary to 
this comment, please verify that it is properly compatible with the client 
profile.

We're re-issuing the Jan SDK in a bit anyway due to some oversights (like 
forgetting to update docs) so if this build is okay then I'll revise that part 
of the release as well.

Original comment by promit....@gmail.com on 31 Jan 2012 at 12:08

Attachments:

GoogleCodeExporter commented 8 years ago 
That seems to fix it. The assembly does show the required metadata:
[assembly: TargetFramework(".NETFramework,Version=v4.0,Profile=Client", 
FrameworkDisplayName = ".NET Framework 4 Client Profile")]
Don't forget that, if you set pre-requisites on the installer, you should 
change these too. 
Thanks a lot!

Original comment by antao.al...@gmail.com on 31 Jan 2012 at 9:11

GoogleCodeExporter commented 8 years ago 
Fixed in January 2012.

Original comment by Mike.Popoloski on 6 Feb 2012 at 4:08

GoogleCodeExporter commented 8 years ago 
Just to warn that the issue has been fixed for the runtime installers but not 
for the SDK installer (Feb 4). They all install SlimDX 4.0.13.43, but the one 
installed by the SDK does not target Client profile.

Original comment by antao.al...@gmail.com on 8 Feb 2012 at 12:06