I am new to windows phone. i need to deploy two xap files as one application to device. In fact we can say that i need to merge them. These two application should also interact between them. Can it be doable?
EDIT:
Firstly my question was the question above. But i understand that there is no way to launch another application inside the other one. So i think it would be meaningless to merge them if ever we could have done so. So i edited the question:
I have one applications xap file and i need to develop another application which should call this applications first page when user clicks some button on develeping application.
The questions are:
Can i import xap file into developing project or xap file of it?
Can i import xap file as a library project to developing project?
Can it be done without source code of the already developed application so that i can interact it from developing application?
Can i import xap file into developing project or xap file of it?
No, WP7 app can't have nested xap files - such app will fail the certification in the Marketplace.
Can i import xap file as a library project to developing project?
If you can unpack the xap file (as it is a zip folder) - you can use dlls to add them as references. So, you can execute some code from that application.
Can it be done without source code of the already developed application so that I can interact it from developing application?
You can try to decompile that app (using dotPeeker for example) if it's legal in your country.
But in general the answer is no.
you cannot just import pure xap into your project and use it
you can extract files from the xap and reference them as a library, call methods in it, etc.
you can also disassemble these libraries into source code and use it in your app directly. For simple projects it might be quite easy, for complex it might not possible at all - the dlls might be obfuscated and you might not be able to use them at all.
As others have said, the answer to these questions in general is "no", but regarding your question "Can i import xap file as a library project to developing project?" - the answer is "maybe, but not directly". If you are just trying to call functions from a DLL that's in the 2nd xap file, then you might be able to extract the DLL from the XAP (by first changing the xap's filename extension to .zip) and then reference that DLL in your project. Of course, if you have the source code for that 2nd xap file, then you're probably better off building the DLL into your VS solution as a separate source project and then referencing that VS project from the calling assembly.
Related
I have developed a C# Winforms application. That application is made by the EXE file and several class libraries DLL files.
It is supposed that if I modified only one DLL file, I could update, in production computer, only that DLL and the whole application should be working as always, with the new features added in the modified DLL. That is not working.
When I add features to one DLL, I need to copy the whole application files, the EXE together with all of the DLL's.
When I modify certain DLL, I modify the Assembly Version of the modified DLL and also of the EXE file. I think that is my mistake.
When I modify one DLL, how can I made the whole application to continue working by just copying the modified DLL to production computer?
Thanks
Jaime
I have a Xamarin Solution were I have two different iOS projects in it - but both of these are sharing the same static content (HTML, JS, CSS++). I'd love to be able to use a target file or similar to be able to include a common file holding a reference to all these files.
When I try and add a directive - it does not seem to respect that at all, not in Xamarin studio, nor when I actually build.
You should be able to make an iOS class library project and include these files in it with a build action of BundleResource. I generally do this with binding projects where the Obj-C library includes a bunch of files you need to include with your app (it works for normal libraries, too though).
When referencing the library, it should copy the files to your application bundle. Keep in mind, however, you probably need to actually have some code in the class library you are calling from the main iOS application project. Xamarin.iOS may strip out the library if code inside is not being used.
I am trying to write a code editor in WinRT that will make the Surface RT and Surface 2 a viable device for people who write code using Visual Studio by bringing light weight code editing functionality to Windows RT in a Windows Store app (No debugging, obviously, just editing files in SkyDrive that are used on a real PC in Visual Studio). This app would include intellisense-like features as a key functionality, and to do this, I would have the user browse to all of the .DLL and .EXE files that their project references. Outside of WinRT, this is relatively simple, but I don't see how to load an assembly from a DLL in WinRT. Is it possible? Remember, I just need to get the string data containing the classes and namespaces contained within the library, and the names of the members of those classes and nothing more.
If it's not possible, it's a shame that a developer like me has to be stopped by all of the restrictions in Windows RT. I am, after all, just trying to write a virus by loading external DLLs and reading the names of the classes, and not running any of the code (sarcasm alert).
Would you really need the dll's and exe's or do you just need the data that will be used? Why not extract the data that your application will use and store that information instead of the complete dll's and exe's?
I finished a project.I am trying create a setup .
My Problem is that :after I create setup project dll files that I used in project added to same folder with my .exe file like
ApplicationFolder(Folder)
Devexpress.Data.dll
Devexpress.Util..dll
.
.
project.exe
but I want to get it different folder.
like
ApplicationFolder(Folder)
MYDLLFILES(Folder)
project.exe(exe file)
how can I make this? Thanks a lot
This is not only a problem of setup. unless you are already handling this in the app.config and/or with appdomain.assemblyresolve event your application will not work at all on the user's machines once those required references will not be available in the same folder if the .exe file.
Surely you could isolate every single file and tell the setup project where to put it but your program has to be modifief to then look for those files in those other locations.
I accidentally faced this problem today, I want to add some separate dll files into the setup package (I have to do this because I can't add reference of these dll files into my C# program , these dll files are of 3rd-party software).
I did as following:
Right click on Setup Project > Add > Assembly and then browse to dll which I need, then press OK button.
These dll files will be included into Setup project, and will be packaged into setup file also.
Hth.
The problem is that Visual Studio setup projects will automatically include referenced DLLs for you so you won't be able to customize their location with these setup projects.
See also the following articles by DevExpress:
How to deploy WinForms applications on client machines
How to distribute applications which use Developer Express .NET Windows Forms controls
The second article explains how to register DLLs copied to a different location.
By the way we're also also deploying a big app using these VS setup projects and our base installation folder is full of DevExpress and other DLLs. I agree that it looks totally ugly and I'd also prefer a clean structure with a lib subfolder, but nobody cares about that. Customers don't start our application from the installation folder, they use the shortcuts.
I am writing a C# Windows application program and I'm using an add-on for creating chart in it,but when I run this program on another windows which has .net framework but not that package it does not work and give me exception.
I want to know how can I correct this problem even with setup file?
and if the answer is setup file then how should I do that?
thank you
When you distribute your package (whether that's through a proper installer or just a zip file or whatever), you should be including the DLL as well. Precisely how to include the DLL depends on what tool you're using to generate the installer.
If, for some reason, you are restricted to distributing a single .exe file, you can use ILMerge to merge an arbitrary number of .NET DLLs into an executable.