Cameyo

Members Login
Username 
 
Password 
    Remember Me  
Post Info TOPIC: message APIRET_DOTNET_REQUIRED


Member

Status: Offline
Posts: 11
Date:
message APIRET_DOTNET_REQUIRED
Permalink   
 


 

Hello!

I create a portable version of the application that installs FrameWork .NET, Java, visual studio. I get a package the size of 900MB, the first time the application runs about 20 minutes.

the problem is that when I try to run the package on a "clean" operating system, I get the message APIRET_DOTNET_REQUIRED. what is the reason?

 



-- Edited by Aaaaa on Wednesday 27th of March 2013 01:23:58 AM

__________________


Member

Status: Offline
Posts: 11
Date:
Permalink   
 

And one more question.
In the package for almost all the .DLL and .RUN files appeared .manifest file. After the first run in the folder VOS appeared only .manifest file (.dll and .run files are absent). RUN module does not start. If I run it manually, it works. but I do not like

__________________


Guru

Status: Offline
Posts: 912
Date:
Permalink   
 

Hello Aaaaa,

Virtualizing .NET is currently not supported.  If you install the appropriate version of .NET on your clean machine, your package should get further than it does in a .NETless environment.

You can force your package to deploy individual files through Package Editor by right-clicking the file under Files tab, choosing Properties, and putting a checkmark in the box for Deployed.  You can deploy all files by using -ExtractAll parameter, e.g. from command line, virtual_package.cameyo.exe -ExtractAll.



__________________


Member

Status: Offline
Posts: 11
Date:
Permalink   
 

Did -ExtractAll.
Can not run some of the modules, for which appeared files *. manifest within the package . for the program installed VC2005_SP1, VC2010_x86_Runtime

__________________


Guru

Status: Offline
Posts: 912
Date:
Permalink   
 

Can the original application be found online for us to download and test?



__________________


Member

Status: Offline
Posts: 11
Date:
Permalink   
 

Unfortunately not.
when creating the package several times warning appears, for example: "New manifest bigger than original: C:\DOCUME~1\Tester\LOCALS~1\Temp\AppPackager\ResManifist.PE (1059->1067)"

__________________


Member

Status: Offline
Posts: 11
Date:
Permalink   
 

saw topic http://cameyo.activeboard.com/t53167019/new-manifest-bigger-than-original-and-incorrect-packaging-of/
but there is no answer

__________________


Guru

Status: Offline
Posts: 912
Date:
Permalink   
 

I sent you a private message.



__________________


Guru

Status: Offline
Posts: 912
Date:
Permalink   
 

Did you see the second private message I sent you?



__________________


Member

Status: Offline
Posts: 11
Date:
Permalink   
 

yes, it did not help.

__________________


Guru

Status: Offline
Posts: 912
Date:
Permalink   
 

Oh, that's unfortunate.  The -ExtractAll parameter worked for the other forum member who posted a similar problem.

Was your original package built on a clean VM?



__________________


Member

Status: Offline
Posts: 11
Date:
Permalink   
 

yes, built in a clean. later built in a clean with FrameWork

__________________


Guru

Status: Offline
Posts: 912
Date:
Permalink   
 

After restoring the clean VM to the state before installing the software, does the Cameyo package work in the clean VM, or do you get the "new manifest bigger than original" error there, too?



__________________


Member

Status: Offline
Posts: 11
Date:
Permalink   
 

yes, I have tried on clean XP and Windows 7

__________________


Guru

Status: Offline
Posts: 912
Date:
Permalink   
 

I'm puzzled that it's not working on the VM that built the package....

If you come across this again with a program that you're able to share, please let us know.



__________________
Page 1 of 1  sorted by
 
Quick Reply

Please log in to post quick replies.



Create your own FREE Forum
Report Abuse
Powered by ActiveBoard