Our web application using oledb for excel import and export, we have install microsoft.ace.oledb.12.0 provider on the local machine, but we have published the website on azure web app , so how to install microsoft.ace.oledb.12.0 provider on azure web app.
please help us.
how to install microsoft.ace.oledb.12.0 provider on azure web app.
TL;DR: You Can Not.
Slightly longer: you do not have the access to the underlying machine or operating system necessary to install COM components. You need to either use a different (non-COM) component that can do the same thing or use a VM where you do control the OS. (Using containers for app services is in preview which might give you another approach, customising the OS as part of the publication of the container.)
Also, Office components are specifically not supported for use in non-interactive processes (eg. web apps), so even if you can use the component you may have odd issues (whether the OleDB provider falls into this classification is unclear).
Related
I am using my_database.accdb as database in my window form application...I want to install it on my client machine without installing ms office.How can i achieve this.I'm using OleDb as connector in my c# application.
you don't have to install ms office in the pc, all you have to do is installing Microsoft Access Database Engine. You can download it from :
Microsoft Access Database Engine
According to Microsoft :
This download will install a set of components that facilitate the
transfer of data between existing Microsoft Office files such as
Microsoft Office Access 2010 (*.mdb and .accdb) files and Microsoft
Office Excel 2010 (.xls, *.xlsx, and *.xlsb) files to other data
sources such as Microsoft SQL Server. Connectivity to existing text
files is also supported. ODBC and OLEDB drivers are installed for
application developers to use in developing their applications with
connectivity to Office file formats.
The Access Database Engine 2010 Redistributable is not intended:
As a general replacement for Jet (If you need a general replacement
for Jet you should use SQL Server Express Edition). As a replacement
for the Jet OLEDB Provider in server-side applications. As a general
word processing, spreadsheet or database management system -To be used
as a way to create files. (You can use Microsoft Office or Office
automation to create the files that Microsoft Office supports.) To be
used by a system service or server-side program where the code will
run under a system account, or will deal with multiple users
identities concurrently, or is highly reentrant and expects stateless
behavior. Examples would include a program that is run from task
scheduler when no user is logged in, or a program called from
server-side web application such as ASP.NET, or a distributed
component running under COM+ services.
We currently have an internal WPF application that serves the business in different ways for different departments. We have a staged rollout process that takes changes through the following steps:
Development (local)
Alpha testing
Beta testing
Live
Developers need to be able to run all of these versions of the application, and some users access the Beta version to sign off new features.
Currently, this is done through a Launcher application deployed via ClickOnce, which downloads and runs the client binaries for the selected version. Each version of the application is hosted by a corresponding web service on the appropriate server (alpha, beta, live).
Does anyone know how this could be done through UWP? We want to future-proof the application and think about support for surface, windows phone etc. But in all cases, developers and users should be able to access the different versions of the application, sometimes even running them at the same time.
Is there support for this kind of concurrent deployment of multiple versions of the same UWP application?
For development these applications may be installed via powershell. From the AppStore you would only get the latest released version but locally you can do what you want.
The required powershell scripts are provided when you deploy the files to the local file system with visual studio. They will even prompt you to create a local developer key if required for your machine.
I have no prior experience working in the .NET stack. Not sure if this is a common requirement. I have developed a simple .NET web service which accesses the COM library provided by a label printer SDK to send print jobs to the printer connected to my machine.
I need to distribute the web service to clients so that it can be hosted on their machines locally. Set up should be minimum - something like an installer which will do the needful to deploy the web service locally.
I assume that any windows machine comes with .NET bundled.
I understand that IIS is the windows equivalent of apache-tomcat. Does is it come bundled with all windows machines? If it does, I figure I can write some scripts to deploy the web service to IIS using the ".deploy" file generated by Visual Studio.
Are there any betters way of doing this ?
So my question is :
How do I distribute a web service that should be be hosted and run locally on the client's machine without forcing the user to download and install a web server and deploy the package?
Edit:
So, I gather IIS is not supported by home editions.
Need Your Help..
I have developed one windows application in C#.Net (stand-alone application). It is basically a Image processing application.
While developing this application I have used Dev-Express controls for better performance. Now I have created the setup file of that application and tried to install it on few machines for testing purpose, while doing this I found that this application is getting install successfully on those machines which has Dev-Express installed on it, but getting failed to install on those machines which do not have Dev-Express setup.
So my question is- "How can I solve this problem..?". Because, as Dev-Express license copy is very costly, "I don't know whether my client will afford it or not". Please Help..!!
You do not need to a separate license for the distribution (see the Licensing FAQ for more information).
However, you need to distribute the corresponding DevExpress runtime assemblies, because they obviously are not installed on clients' machines. This approach is common for distributing 3-rd party products. Consult the DevExpress support for further clarification.
Situation: I have web application in my pc, who manipulates docs to generate pdfs with no problem. I configured my dcomcnfg to work fine because I had the problem with access permissions the COM.
The problem: I have to put the website in the server. The server has Win8 Enterprise. Doesn't have Visual Studio installed, only framework 4.0 and the Word Office. When I try to generate pdf it always return this error: Retrieving the COM class factory for component with CLSID ...
I run dcomcnfg and customized all permissions to IIS service (doesn't work and put to) Everyone. I Set all Launch and Activation permissions to allow Everyone, I also set Access Permissions and configuration permissions.. And still don't work.
I have to register the dll in server?(How I do it?)
I need more configurations?
I Have to install all Office?
ps: Office 2013
while it is not recommended to use this on server, there is a possible solution:
impersonate the admin in the asp.net application:
http://msdn.microsoft.com/en-us/library/aa292118%28v=vs.71%29.aspx
it may have security issue.