Am supposed to develop a windows Service Controller application programming interface (API) driver service drivers. in visual studio 2017
Could someone put me through on the library or C++ template i need to install in Visual Studio.
Since you're using Visual Studio 2017, click on the Open Visual Studio installer to install a missing component
"ASP.NET web development". When the installation finishes, create a new project and write your windows service with "Windows Classic desktop".
Check out this link : https://msdn.microsoft.com/en-us/library/system.serviceprocess.servicecontroller(v=vs.110).aspx
Your driver service requires an in dept research and programming experience.
In my experience in writing windows service, I write it in C# and I write the driver service in C++.
Related
The goal
I would like to use a Windows Server 2016 (x64) for remote debugging of UWP applications. The reason? My working PC still runs a Windows 7 instance and it is not possible to deploy an UWP app on a Windows 7 machine.
The problem
I have already installed the Remote Tools For Visual Studio 2015 on the Windows Server 2016 machine and started it on port 4020. Authentication mode was set to "None". I have enabled Developer mode on the server as well. Also I have set up my project in Visual Studio to use the remote machine for debugging.
The problem is, whenever I try to deploy (just deploy, not even debug) my solution to the server, the following happens:
Visual Studio shows the following output:
Deploy started: Project: MyProject.UI.Uwp, Configuration: Debug x86
Starting remote deployment...
Reading package recipe file "C:\SourceCode\MyProject\MyProject.UI.Uwp\bin\x86\Debug\MyProject.UI.Uwp.build.appxrecipe"...
and then hangs forever.
In the meantime, remote tools on the server show the following output:
UserAbc connected.
This indicates there must be at least some communication between my Windows 7 PC and the target Windows Server 2016 machine.
No error message is displayed whatsoever (neither in Visual Studio, nor in the Remote Debugger).
The question
Any idea why the deployment hangs forever without an error message? Or am I trying to achieve an impossible task? Is the Windows Server 2016 capable of running UWP apps at all?
Update
I installed VS 2015 Update 3 directly on the Windows Server 2016. I was able to create and debug a simple UWP app directly on the server so the server is clearly able to run an UWP app. However I am still unable to make the remote debugging working. Maybe the problem is completely on my local Windows 7 PC and has nothing to do with the Windows Server. It is strange that the process hangs while "Reading package recipe file". Could it be that an antivirus is intercepting?
Thanks for your feedback. There is a similar issue when I try to deploy the UWP project to a remote machine on Windows 7. We have communicated about this using our internal channel. Unfortunately, Visual Studio 2015 or Visual Studio 2017 doing UWP development on Windows 7 is not a recommend scenario.
For Visual Studio 2017, using Tools for UWP App Development is not applicable on Windows 7. See Visual Studio 2017 Support for Windows Development.
For Visual Studio 2015, the official support for Windows Universal is "Build only". We can use Visual Studio 2015 to build UWP apps on Windows 7, but some other Visual Studio features for Windows Universal development may be degraded. See Visual Studio 2015 Support for Windows Universal, Windows Store, and Windows Phone App Development.
To develop Windows Universal Apps, Windows 10 is strongly recommended. With Windows 10, you can get the best experience of UWP development.
I am trying to install UCMA 4.0 SDK and it looks like one of the prerequisites is a Lync Server 2013 (Bootstrapper Prerequisites Installer Package, Core Components).
Is this supposed to be a fully configured server ? I have a running Lync Server on the Network... on a server, hovewer, I don't want to develop on it. Will the Lync Server installed during installation of the SDK be just a couple of required libs and stuff or is it supposed to be a working Server, i.e. will it interfere with the running Server in the Network ?
Is there maybe a how-to-setup-ucma-dev-environment-for-noobs tutorial out there ?
No you do not need a full Lync/Skype environment to install the UCMA SDK and develop locally, however will need to have a properly configured application server that is registered with your Lync environment to be able to run your UCMA application.
And no the SDK will not deploy Lync.
To be honest to develop a UCMA app all you really need is the Microsoft.RTc.Collaboration.dll usually found in C:\Program Files\Microsoft UCMA 4.0\SDK\Core\Bin once the SDK is installed.
If you are going to run as development server, install visual studio first.
Run UCMA 4.0
Install Core components by navigating to the following path and run OCSCore.msi
C:\ProgramData\Microsoft\Lync Server 2013\Deployment\cache\4.0.7577.0\Setup\
After that, go the following path (Cd C:\Program Files\Microsoft Lync Server 2013\Deployment) and run bootstrapper from command prompt>>
Bootstrapper.exe /BootstrapLocalMgmt /MinCache
After all the steps, you can start provisioning for your application.
When I installed Microsoft Visual C++ and C# 2008 Express, I got "Microsoft Windows SDK for Windows Server 2008" added in.
I want to know if I can remove it and still have all the functionality of Visual C++/C#.
Strange, I remember it was shipped with Vista RTM headers (The Microsoft Windows Software Development Kit Update for Windows Vista version). Looks like Microsoft updated the SDK bundled with Express.
Anyway, the SDK is responsible for a lot of features in Visual Studio. For example, Visual Studio invokes sgen.exe to generate XML serializer assemblies, and call rc.exe to compile a resource script. Chances are you can't get away without it if you are not writing hello-world apps.
My add-in targets Outlook 2007 and was built using C# with Visual Studio 2010. I have run into problems deploying this to different target machines by means of the SETUP.exe and "manifest" built by the Publish Wizard of Visual Studio.
My latest attempt to get this deployed to a target PC (i.e. one typical of other users where this will be deployed and lacking my development environment) gives strange problems:
the add-in installs OK (i.e. Setup had no complaints; program appears properly in Control Panel)
visiting Tools -> Trust Center -> Add-ins shows that my just-installed add-in is Inactive
clicking Go.. for the Manage COM Add-ins dialog & checking the box for mine then the Add.. button fails
a window looking like a browse dialog box titled "Add Add-in" comes up with "No items match your search" in the right-hand pane; at the bottom of this window is an empty textbox labeled "File name:" and a choice of "Executable Files" or "All files" for a file type. The add-in remains "inactive".
It is not clear to me what this dialog needs at this point to make it "active" (Load at Startup was part of the choices here).
NOTE:
The 2 projects in this solution were compiled for a "target framework" of .Net 3.5 resulting in references to DLLs such as Microsoft.Office.Tools.Outlook.V9.0 and his companions (I guess that is "VSTO 3.0 ??).
This solution launches Outlook properly on the development PC and the add-in is loaded successfully and runs as expected (against Outlook 2007 and/or Outlook 2010); so this seems related to deployement only.
Could there be a bug in the stuff built by the Setup wizard that comes with Visual Studio 2010? I read somewhere that the "manifest" can be "corrupt".
EDIT-UPDATE 3/31/2011:
I think I found the answer. I believe by using the "Publish Wizard" in VStudio which produces a SETUP.EXE, I was trying what is called "ClickOnce" deployment. Secondly, this addin for Outlook is NOT a "document level" addin but instead a "machine level" addin. Given these discoveries of better terminology, I found this at http://msdn.microsoft.com/en-us/vsto/ff937654.aspx:
"You can use ClickOnce to create and install self-updating applications with minimal user interaction. This has an automated mechanism for easily distributing updates to your application. However, ClickOnce is not capable of deploying components that require administrative privilege such as machine level add-ins. For solutions that require administrative privilege you can use Windows Installer to deploy a Visual Studio Tools for Office customization."
So, I will try to make a Windows Installer. Any confirmation would be appreciated.
I am confident the ClickOnce style of deployment will NOT work for my machine level add-in for Outlook 2007. Therefore, I am answering my own question by stating only that this requires a Windows installer (and setup) that can built with the properly chosen Visual Studio template.
The sad news is that in my testing of said installer .msi and associated setup.exe for the pre-requisites the install to my target machine went well but when I test the operation of the addin itself inside Outlook I get a terrible APPCRASH event in Outlook.exe:
Problem signature:
Problem Event Name: APPCRASH
Application Name: OUTLOOK.EXE
Application Version: 12.0.6550.5003
Application Timestamp: 4d10fbc4
Fault Module Name: kernel32.dll
Fault Module Version: 6.0.6001.18215
Fault Module Timestamp: 49953395
Exception Code: e0434352
Exception Offset: 000442eb
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033
Additional information about the problem:
LCID: 1033
Brand: Office12Crash
skulcid: 1033
So the answer is that ClickOnce is not appropriate. The .msi appears to properly install the add-in but at runtime it blows sky high. Remember the addin works properly at runtime when launched via Visual Studio. Why does deployment have to be so damned difficult?
I have published a WinForms application from Visual Studio 2010. It uses .NET 4.0. in the prerequisite dialog in Publish pane I selected .NET 4.0 Client Profile and Windows Installer 3.0. After publishing application to disk, I migrated it to client's computer which first installed .NET Client Profile and after reboot it gave following error message:
Unable to Install or run application. The application requires that assembly, Microsoft.ReportViewer.Common version 10.0.0 in global assembly cache first.
After this message the installation process exits. I'm using .NET's report in my project (not Crystal Reports).
You have to deploy the ReportViewer controls separately.
Check here on MSDN for more information: Deploying Reports and ReportViewer Controls
The ReportViewer control redistributable is a self-extracting file named ReportViewer.exe that includes an .msi and other files. You can find ReportViewer.exe at the following location:
%PROGRAMFILES%\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages\ReportViewer\ReportViewer.exe
You can also download it from the Microsoft Download Center.
[ . . . ]
The type of control you are using
determines where ReportViewer.exe
should be run.
For ASP.NET applications, run
ReportViewer.exe on the Web server
that hosts your application. This must
be done by a server administrator.
For Windows Forms applications,
include the controls as an application
prerequisite so that they are
installed automatically with your
application. You can use the
bootstrapping application to automate
this step:
Open the project properties page.
Click Publish, and then click
Prerequisites.
Select Microsoft Visual Studio 2010
Report Viewer, and then click OK.
Publish the application.
During application installation, a
check is performed on the local
computer to see if ReportViewer is
already installed. If it is not
installed, the Setup program will
install it.
I guess this is probably a new VS2012 feature, but you now can deploy Report Viewer (and the SQL Server CLR Types) with Forms / WPF click once installations.
Open the project properties page.
Click the Publish tab, and then click the Prerequisites button.
Select Microsoft Visual Studio 2012 Report Viewer, and SQL Server
CLR Types then click OK.
Make sure that the Download prerequisites from the component
vendor’s website option is checked. This is the only supported
option. Then, click OK.
Click the Options button.
In the Deployment tab, specify a deployment Web page and select the
Automatically generate deployment web page after ever publish
checkbox.
Click OK and publish the application.
look at this: Running ReportViewer.exe
both we are gave you same link. it will help you
Download and install Microsoft Report Viewer 2012 Runtime CTP from following url...
http://www.microsoft.com/en-in/download/details.aspx?id=27230
I had same problem but it solved after install the above...
Thanks...
I had the same problem for months, one machine cat v.11 installed (manually by adding some components) and another had v.10 (from the ms framework itself), when I did the publish from my machine, it gave the error.
here is how I fixed it,
In Nuget, there are 2 packages,
Microsoft.ReportViewer.Windows (Microsoft.ReportViewer runtime 2012) and
ReportViewer.Common 10.0
I installed them both, now its working quite all right
Open project properties Alt+Enter.
Click on publish tab.
Click on prerequisites select Microsoft visual studio report viewer.
visit this website for more detail
https://msdn.microsoft.com/en-us/library/ms251723.aspx