It is not clear to me if I can use fabricUI icons & Segoe UI font in my project
According to this license which can be found in the project repository
I have found this StackOverflow question which is linking to this issue in the Fluent Repo
Fabric's assets (fonts, icons, and product logos) are part of Microsoft's brand, and can only be used in apps & services--including commercial ones--that connect with Microsoft products. These include Add-ins for Office, web parts for SharePoint, and other extensions for Microsoft products. This applies to usage of the assets in application code itself as well as any designs produced by the toolkit.
I am building a commercial application that can be used as an Excel add-in and have a separate URL where can be used as a standalone web app. Can I use Fabric Icons and SegoeUI font in both places?
My application is 100% MS services dependent (MS Auth, multiple azure services) and I would like to have the same design.
Related
I am trying to understand how to develop add-ins/macros in JS for Office, do I need VSTO for it or does it run from Office somewhere?
I did understood that Microsoft is making the first steps toward replacing VBa with JS and impemented an API to develop macros in Office.Js simmilar to the one Google has for it's Docs. But where can I find a development enviroment for Office.js?
The new web-based add-ins are basically a web application executed in the context of the Office application, either on the Desktop (by embedding a browser, IE11 at the moment) or in the browser (Office Online) where everything is web-based already.
The add-in can be hosted on any web resource you like. You just need to specify a source location URI.
Settings and metadata of the add-in are defined in a manifest file. The article Office Add-ins platform overview describes it very well.
Development can be done in any editor or IDE suitable for coding web apps. There is no Alt+F11 VBA IDE anymore, but you may try the Script Lab add-in, a Microsoft Garage project that allows you to try out some code directly in Office and share code snippets. It includes a great collection of sample code too.
The new WebApplications are hosted on a Webserver. You can develop Office Apps with Visual Studio.
Here is a good course for developing Office Apps including an overview of the Javascript Office API:
https://mva.microsoft.com/en-us/training-courses/introduction-to-office-365-development-8329
I went to Office UI Fabric's site today and noticed "Fabric.js" was removed as an option.
Is Microsoft discouraging it from being used?
Last version update for Office Fabric JS (office-ui-fabric-js package) happen 8 months ago and the latest commit was performed 3 months ago. In the same time office-ui-fabric-react package is regularly updating and moving on full speed. Make up your own conclusion. By the way, FYI Office UI Fabric JS has it's own website.
Office UI Fabric JS is now officially dead. Fabric React and Fabric Core are the recommended libraries to use going forward.
We received this email from the Office 365 Message Center today:
Do you have any internal line-of-business apps or add-ins that your
developers have made to look like Office? If so, they may be using a
library called Fabric JS. We want to inform you that we will no longer
be making updates to the Office UI Fabric JS, beginning October 1,
2019.
Over the past few years, the team behind Office UI Fabric has been
working hard on Office UI Fabric React. It is a robust framework for
building experiences that fit seamlessly into a broad range of
Microsoft products. It includes many full-featured, production-ready
UI components, utilities for accessibility, styling, iconography,
toolkits, resources for designers, and more. Having reached this
milestone, we’re simplify our offering of UI frameworks. Going
forward, we recommend developers use Fabric React and Fabric Core to
build experiences that align with the Office user experience. As a
result, October 1, 2019 marks the official end of support for Office
UI Fabric JS. While we are no longer actively developing new features
or fixing bugs, all existing versions of Fabric JS will remain
available on Microsoft’s CDN and solutions built with Fabric JS will
continue to function normally.
[How does this affect me?]
If you have, or are building, applications that leverage Office UI
Fabric JS, you’re welcome to continue using it; however, Microsoft
will not fix any bugs and offers no guarantee that components will
stay current with latest Office user experience.
[What do I need to do to prepare for this change?]
If you have, or are building, applications that you would like to
ensure fit seamlessly into a broad range of Microsoft products,
instead of using Fabric JS, we recommend using Fabric React or Fabric
Core. To learn more about Fabric React and Fabric Core, please see the
Additional Information.
I've studied the link below:
Storefront Source Code Getting Started.
According to the "Configuring content connection string" Section, I realized that the need to be placed physical address of "cms-content" of admin.
but We've deployed web applications(admin and storefront) to dedicated server.
So for a configuration with these conditions I read the link below:
Deploy web applications to dedicated server
But this link is not yet clear how the "ContentConnectionString" was initialized.
ContentConnectionString storefront setting pointed to place where themes files stored and has default value ~/App_Data/cms-content.
VC platform, with installed module vc-content allows to manage themes files from manager UI and have similar setting CmsContentConnectionString.
If storefront and platform have installed on same Azure apps or dedicated server this both settings should pointed to same physical place and have follow valuesprovider=LocalStorage;rootPath=~\App_Data\cms-content in platform Web.config and provider=LocalStorage;rootPath={ vc-platform physical path}\App_Data\cms-content in storefront Web.config.
For case when VC platform and storefront have separated installation need to use azure blob storage provider=AzureBlobStorage;rootPath=cms-content;DefaultEndpointsProtocol=https;AccountName=yourAccountName;AccountKey=yourAccountKey to share themes files between storefront and platform.
We strongly recommend use store and change your theme in GitHub repository and use CI (continuous integrations tasks) for update themes on production and use admin UI theme management only for emergency fixes or other not historical changes.
I want to generate word documents from my ASP.net MVC 6 website. I've implemented several ways to generate a document in a POC : DocX, NetOffice, OpenXml, COM Interop objects. I was seduced by it.
I made a Console App to test and it works.
But, with ASP.net MVC6, we can't reference Console App's or COM Assemblies.
We need to create "Console App (Package)".
How can I add COM Assemblies to my ASP.net MVC 6 website ?
Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office may exhibit unstable behavior and/or deadlock when Office is run in this environment.
If you are building a solution that runs in a server-side context, you should try to use components that have been made safe for unattended execution. Or, you should try to find alternatives that allow at least part of the code to run client-side. If you use an Office application from a server-side solution, the application will lack many of the necessary capabilities to run successfully. Additionally, you will be taking risks with the stability of your overall solution.
You can read more about that in the Considerations for server-side Automation of Office article.
Consider using third-party components designed for the server-side execution or if you deal with open XML documents you may use the Open XML SDK, see Welcome to the Open XML SDK 2.5 for Office for more information.
Is it possible to develop a web-part in ASP.NET (framework > 2.0), to have a sandbox architecture, and deploy those web parts inside Share Point 2010 and/or MOSS 2007
we donot want to use any SharePoint dll reference with web parts we develop.
we refer to the url, section at http://msdn.microsoft.com/en-us/library/ee539417.aspx (section Web Parts in Sandboxed Solutions)
i referred the following How Tos, hope it helps some one ..
http://blah.winsmarts.com/2009-12-SharePoint_2010_Sandboxed_Solutions__The_basics.aspx
_http://www.sharepointdevwiki.com/display/sp2010/SharePoint+Sandboxed+Solutions
_http://www.endusersharepoint.com/EUSP2010/2010/04/05/introduction-to-sharepoint-2010-sandbox-solutions-for-site-collection-owners
I've just hit this problem - looks like it's not meant to be possible which is really annoying.
See: http://msdn.microsoft.com/en-us/library/gg615454.aspx
Specifically:
Application pages, mobile pages, and user controls (.ascx files) cannot be deployed in a sandboxed solution.
However, there is a workaround (hackaround!) here:
http://stefan-stanev-sharepoint-blog.blogspot.com/2010/02/visual-sandbox-web-parts-possible-after.html
I'd love to have a better way!