We have an on-premise SharePoint 2013 farm, and we have a few .mpp files stored in a library.
.xls and .doc files in the library were opening in the respective Web Apps, but the .mpp files were not.
I was getting an alert asking if I wanted to allow the website to open an app on the computer.
On selecting Allow, it was showing a prompt for getting an app for ms-project from the Store.
I changed the library to open all files in client applications, but the behavior for .mpp files persist.
Curious case is that if I open 'View properties' and click on the link, it opens in the client application.
How can I force the .mpp files to always open in the client?
We fixed this with a very simple change in the view.
We unchecked the default Name (linked to document with edit menu) column and replaced it with Name (linked to document).
Now we are able to open the .mpp file in the client application.
Related
I have explored expo FileSystem APIs but it doesn't give any option to store files on app's internal folders.
All the files saved using createFileAsync API with Document dir are showing up on user's device file manager app.
Is there any way to do it without ejecting expo?
I am trying to direct the Root Context to the Developer Portal in WSO2 APIM tool, i followed this docs:
https://apim.docs.wso2.com/en/latest/develop/customizations/directing-the-root-context-to-the-developer-portal/
but i have no idea how i can open this file
org.wso2.am.styles_3.2.0.jar
and edit the component.xml.
Thanks.
Follow these steps :
Right click on the JAR file.
Click Open with other Application.
Select the Archive manager according to your OS.
Open the component.xml file that is inside META-INF directory using a text editor.
Edit that text file and Save
Restart the server
The following errors pop in the log when publishing web project to folder.
....
Publishing folder /...
Publishing folder bin...
Publishing folder bin/es...
Publishing folder bin/roslyn...
Unable to add 'bin/roslyn/System.IO.FileSystem.dll' to the Web site. Unable to add file 'bin\roslyn\System.IO.FileSystem.dll'. The process cannot access the file because it is being used by another process.
Unable to add 'bin/roslyn/System.IO.FileSystem.Primitives.dll' to the Web site. Unable to add file 'bin\roslyn\System.IO.FileSystem.Primitives.dll'. The process cannot access the file because it is being used by another process.
Unable to add 'bin/roslyn/System.Reflection.Metadata.dll' to the Web site. Unable to add file 'bin\roslyn\System.Reflection.Metadata.dll'. The process cannot access the file because it is being used by another process.
Unable to add 'bin/roslyn/System.Security.Cryptography.Algorithms.dll' to the Web site. Unable to add file 'bin\roslyn\System.Security.Cryptography.Algorithms.dll'. The process cannot access the file because it is being used by another process.
Unable to add 'bin/roslyn/System.Security.Cryptography.Primitives.dll' to the Web site. Unable to add file 'bin\roslyn\System.Security.Cryptography.Primitives.dll'. The process cannot access the file because it is being used by another process.
Unable to add 'bin/roslyn/System.ValueTuple.dll' to the Web site. Unable to add file 'bin\roslyn\System.ValueTuple.dll'. The process cannot access the file because it is being used by another process.
Unable to add 'bin/roslyn/VBCSCompiler.exe' to the Web site. Unable to add file 'bin\roslyn\VBCSCompiler.exe'. The process cannot access the file because it is being used by another process.
Publishing folder bin/zh...
...
Publishing folder Views/WFDefs...
Publish failed. Target file://machine/d$/PATH.
If i publish using web publish it works, but the real target doesn't support web publishing.
Note: VBCSCompiler is not running.
I had the same problem with my application with Visual Studio community 2017. In my case the solution was simple, I only deleted all the files inside the directory bin (C:\Projects\DotNet\ApplicationName\bin) and after I recompiled the application.
I hope it can help you.
Had this same issue in Visual Studio 2017 Community Edition. As your question came up in Google but no answer, I thought I'd add to it.
I found Process Explorer from Sysinternals helped me a bunch.
Open sysinternals and go to Find -> Find Handle or DLL... or (Ctrl + F) and search the file that's being held open. In my case "System.IO.FileSystem.dll"
The search results showed two instances of MSBuild and one VBCSCompiler was hanging onto the files. Worst case, I just killed the process tree, built the project and all was well again.
Related answer: https://serverfault.com/questions/1966/how-do-you-find-what-process-is-holding-a-file-open-in-windows
If you try to publish asp.net web app in Azure and getting above error then try to UPDATE the Microsoft.CodeDom.Providers.DotNetCompilerPlatform package to V1.0.7 or later. Initially, in your application, there will be Microsoft.CodeDom.Providers.DotNetCompilerPlatform version 1.0.5 then uninstall and then install the latest version V 1.0.7 or later of it. Clean your solution and build. Now you will be able to publish your web app in Azure using Visual Studio 2017.
I'm creating and app which adds text field with custom JSLink.
Everything works fine when I store js files in sharepoint library, but when I reference files which are store in the "app web" (site where the app has it services and sites), this .js files are not loaded. No error, just nothing happens.
How can I reference JSLink file which is out side of sharepoint library?
You can not to do it. Because SharePoint App has isolated architecture. Same situation with host web. You cannot set JSLink property on host web to link of JS file from App web.
I made a complete copy of the old web application.
Copied it to the new server.
Made appropriate SQL Server changes and it does not work.
ELMAH Version: v1.0.3705
OS: Windows Server 2012
IIS 8
I believe I found your answer. You need to grant your IIS AppPool permission to modify (or write) to the path you have instructed ELMAH to write the XML. To do this, bring up Windows File Explorer, locate the path and folder where ELMAH is writing those XML, right click to get folder menu and select properties, locate and click on the tab labeled SECURITY, and follow the instructions described in this URL:
http://www.iis.net/learn/manage/configuring-security/application-pool-identities