A developer created a web front-end and deployed on server. Unfortunately when the vue application was developed I did not receive the original vue files so all I have access to are the files deployed on the server.
I'm unsure how vue works and if deployment means that the web application is compiled. If this is the case, is it essential to have the original vue project to make changes ?
What disadvantages will I encounter without the project file?
Thanks
If the original developer used VueJS-cli to develop, you should have the source code at src folder.
The deployed assets are generated in a build phase, and keep apart from source code.
The deployed code is in folder dist in server.
If you only received the dist folder (the compiled assets), maybe it is a difficult to reverse engineer the code, because you only have the minified and uglified version of the source code.
I have several DLL files in C:\RLM85LTD\
e.g.
C:\RLM85LTD\Interop.MSXML2.dll
My app from the Debug folder is in a folder on my desktop called my apps. when I opened the app from my apps folder it does not work unless the relevant DLL's are in my apps folder.
How can I get the app to work with the DLL in C:\RLM85LTD.
I have an asp.net core 3 application deployed on IIS. I made this by publishing the website on a separate folder, and reference that folder when I added a new application in IIS. It works, I can access it from different computers, but this folder doesn't get updated when I'm doing modifications and compile the project. I always have to publish it whenever I make small modifications. How can I overcome this situation?
This is how my folder looks like after publishing my project.
I am working on a .NET CF 3.5 application. There are few external files\assemblies that the application is consuming. These files are not part of the project, therefore while debugging when I deploy the project, these external files are not deployed to the device.
Is there any way I can deploy these files with project without including them in the project?
You can't get Studio to deploy arbitrary files without telling it what files to deploy. The only way to tell Studio to deploy files is to either add the files to the project (as a Resource or a Content file) or by adding a reference to them (for .NET assemblies).
Questions:
Are XAP files self-contained?
Do they link in all DLLs I have referenced in the project?
If I need to distribute my app, is all I have to do is hand someone the XAP file?
By default, yes. For alternatives, see answer 3.
By default, all except the core DLLs installed by the runtime; it will contain anything from the SDK, Toolkit, 3rd party controls, or your own libraries.
By default, yes. However, there is an option as of Silverlight 3 to package certain assemblies (for example anything from the SDK) into separate ZIP files, which are downloaded separately. In Visual Studio, look in the project properties for a checkbox called "Reduce XAP size by using application library caching." This option toggles whether to create/use the ZIP files or not. Enabling the ZIP option allows multiple Silverlight apps to share the dependency on the ZIP files, so that instead of packaging everything into the XAP every time, you just download the ZIP for one app, and it's saved in the browser cache for other apps.
As for the general contents of the XAP file, there are 2 important bits:
Foo.dll - your project's main assembly (renamed as appropriate)
AppManifest.xaml - describes the requirements for you app, e.g minimum runtime version required, the entry point into Foo.dll, and other settings, including Out-of-browser settings, or whether to use the Library caching feature mentioned above.
Anything else is just content used by your app.
Silverlight XAP files can be tricky if you're using anything other the the core silverlight assemblies (eg. SilverlightToolkit).
XAP files are just zip files - open one up and take a look. They are self contained to the extent that any custom/extra dlls are included - the standard Silverlight assemblies will be installed when a user installs Silverlight.
References to dlls are required in the .proj files for every assembly that will be used. Ie. unlike other project types, if one project references another project, both projects need to reference all dlls used by either project.
You should be able to just hand someone the XAP file if you want - but Silverlight was designed to be used in browsers, so you will need to include the generated test page at least. The best, and most useful, is to provide a publicly accessible web page that hosts your silverlight app.
HTH.
Even though this question is already answered, i'm going to throw this one in too because it hasn't been mentioned yet.
You mention that you are using SL4 - if you are running out of browser (OOB) then you can just ship the XAP file, and use sllauncher.exe (2) to "install" it to the client machine. As part of that install you can also specify where updates are to be sourced from, which is important for when you find bugs or the requirements change.