/build/static/layout/Breadcrumb_cap_w.png

Question about dotnet capture

http://www.messagebottle.org/packages/wise%20capture.rtf

As you can see in the uploaded file, you see that apart from files that are captured in the "global assembly cache" (as you see in the first picture) there are also file captured hardcoded under C:\windows\assembly\GAC\.

Do I have to leave this files in the capture. Why are they not part of the "Global Assembly Cache" anyway ?

0 Comments   [ + ] Show comments

Answers (5)

Posted by: anonymous_9363 11 years ago
Red Belt
0
I make that TWO questions. Wanna delete one of them?
Posted by: ikke 11 years ago
Senior Purple Belt
0
Extra info: I am not talking about capturing the prerequisite dotnet, I am talking about capturing an application with dotnet assemblies.
Posted by: mekaywe 11 years ago
Brown Belt
0
It shouldn't cause harm to your application.. Leave them as they are in your capture
Posted by: anonymous_9363 11 years ago
Red Belt
0
You could have saved yourself hours of waiting by creating two packages, one with the files in place and one without, then compiling and testing both.

Try these instructions which the magic of the internet turned up.
Posted by: ikke 11 years ago
Senior Purple Belt
0
The problems were caused by the fact that the installer wrapper of the application was also installing a version of dotnet 1.0.

I left it out of my capture and it did not have any issue anymore.

Thank you all for the valued advise !
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ