.Net 4 Client Profile + System.Design

Add-in Express™ Support Service
That's what is more important than anything else

.Net 4 Client Profile + System.Design
 
Mimi Yang




Posts: 120
 Joined: 2010-02-01
This is the same problem as

http://www.add-in-express.com/forum/read.php?FID=5&TID=7613&MID=38266#message38266

As the add-in has been released, is there a way to force the loader to use .Net 2?

Thanks a lot.
Posted 13 Aug, 2010 23:58:51 Top
Muller Stephan




Posts: 50
 Joined: 2010-03-11
I am also interested in this topic.
Posted 14 Aug, 2010 13:54:09 Top
Eugene Astafiev


Guest


Hi Muller,

Do you mean the .net 4.0 Client Profile or System.Design.dll dependency issue? Could you clarify this to me?

As the add-in has been released, is there a way to force the loader to use .Net 2?


Nope. You can set the target framework in the properties of your add-in project only.

BTW Could you specify version and build number of Add-in Express you use?
Posted 16 Aug, 2010 04:12:10 Top
Muller Stephan




Posts: 50
 Joined: 2010-03-11
Hi Eugene,
sorry for my late answer, I did not monitor this thread.

I mean the .net 4 framework. The problem is that when I set the framework to 2 (so that most users do not have to update), the program won't run (or at least not install) if the user has .net framework 4.

Do I get that right? (It's what I have from tests on Win XP). Is there any solution or recommended way to handle this?



Thanks 8)
Posted 02 Sep, 2010 01:27:19 Top
Eugene Astafiev


Guest


Hi Stephan,

The adxloader always loads the latest version of the CLR. However, the add-in with target framework 2.0 should be loaded correctly. Could you please show me the adxloader.log file from a user's problematic PC?

BTW Typically you can find the adxloader.log file in the <My Documents>\Add-in Express folder.
Posted 02 Sep, 2010 04:55:00 Top
Muller Stephan




Posts: 50
 Joined: 2010-03-11
Hi Eugene,
the problem is that when
1. I use .net Framework 2
2. I create a default setup project
3. I install the Add-in on the target (w/out any .net framework).

The installer will ask to install the .net framework. It'll redirect to the Microsoft page which offers .net 4.

The user will install .net 4.

Next time the user starts the add-in, he will again be prompted that .net 2 is needed.

So it's basically more a setup issue than a loader issue.



Kind Regards
Stephan
Posted 03 Sep, 2010 01:53:47 Top
Eugene Astafiev


Guest


Hi Stephan,

Thank you for the explanation.

Please make sure that you set the target framework property of the add-in project to .net framework 2.0. Also please check out Launch conditions of the installer. What .net framework version do you have in the launch condition?
Posted 03 Sep, 2010 03:51:22 Top
Muller Stephan




Posts: 50
 Joined: 2010-03-11
Hi Eugene,
yes both the target framework and the requirement are set to 2.sth.

However because setup opens IE with the .net 4 download, it does not help.

I think setting the URL for the .net requirement in the setup to

http://www.microsoft.com/downloads/details.aspx?FamilyID=0856eacb-4362-4b0d-8edd-aab15c5e04f5&displayLang=de

fixes the problem, since the setup should then redirect there.

Update: yep, that fixed the issue :), thanks for the hint!



Kind Regards
Stepha
Posted 05 Sep, 2010 14:16:48 Top
Eugene Astafiev


Guest


Thank you for the good news, Stephan! Awesome :-)

Good luck with your project!
Posted 06 Sep, 2010 08:45:07 Top