Our company has an existing web application in ASP.NET MVC and we would like to integrate the functionality to directly (seamlessly no 2nd authentication) open a remote app in the browser using the Microsoft RDS HTML WebClient.
I have already looked around but the only things I can find is customizing the existing webclient's pages in very limited ways.
I'm hoping someone here could point me in the right direction. I have also found 3rd party RDP solutions like myrtille and guacamole.
Related
I'm building a blockchain-themed web browser in a C# .NET Windows Form Application and want to allow users to view sites using the dat:// protocol. I have found several repositories online but none of them seem to be for C# or close to what I want.
I've already tried using the Dat P2P Protocol Firefox addon but the setup was too difficult and I'd have to figure out how to add extensions to the browser in the first place.
Currently there's only one implementation of Dat, which is built for NodeJS. There's a rust implementation being developed as well.
I am trying to get my company to start using SSRS for reporting but I realized something today that I have never tried to use SSRS outside the local LAN before. Our application is external facing on the internet and if I implemented SSRS, I would need to be able to access the Report Manager via an external URL.
It is setup and configured currently, but I can only use it locally on the company domain. I tried searching the web for how to configure this and what best practice is but I didn't really get anywhere.
I imagine it would not be good to set it up on the same server that the database is hosted on? Has anyone done this before? I have setup one application that was inherently not meant to be external before to be external and it was a pain in the ass. :D Course, that application had to be proxied through Tomcat to IIS.
We have a developed an intranet web application build on ASP.Net MVC 4 and SSRS 2012, which is live for past 2 years.
Now we planning to host the same in internet. We are having a bottle neck now for SSRS. As SSRS web access is not ready to use externally (internet).
I also checked for SSRS custom authentication which again not much recommended by Microsoft!
We are looking for something like a proxy (web application) to the SSRS web access, which can be hosted as a web application in IIS along with other services.
Is there any ready to use references / tools available.
Update : For better understanding
We are rendering the ssrs reports inside the Asp.Net mvc razor views using iframe.
And also we are using ssrs for export to various formats.
Use the ReportViewer control to hide the SSRS from the internet.
The connection to the SSRS is from your web servers, not from the internet
I am helping to build Elpis, which is an open source pandora music player, built with C# and WPF.
Now what i want is to add an HTTP API so that the user may control the program through a browser, like play/pause, like/dislike the current song.
The point afterwards is to control the program through a mobile device accessing the HTTP API.
How exactly should i build the HTTP API so that it can control it?
Github for the project: https://github.com/adammhaile/Elpis
Without knowing why exactly you want the user to control a GUI application via the browser, it's hard to give you good advise.
Assuming you are running your GUI on Windows, take a look at OWIN and the project Katana. They allow you to easily host HTTP interfaces in your own application.
It may be overkill for your project but I would suggest using ASP.NET Web API so that you can build backend web services.
The easiest way to do what you want, assuming you really want to "control the GUI remotely" is to just install TeamViewer on your PC and on your mobile device. Then you could remote in and completely control your GUI.
But I what I think you're after is something more like Google Music. Where you can stream your music through the Internet and onto your mobile devices. If this is the case, I recommend you look at the ASP.NET Web API.
It's not hard to build a web server in C#. You can embed it into your application, and expose parts of your application to HTTP endpoints as an API. You can use the HttpListener class which is part of .NET, and do everything from the ground up yourself. Or you could use something like Nancy, which is a lightweight framework that provides a lot of useful scaffolding like URL routing.
Ended up using Kayak(https://github.com/kayak/kayak) for my self-hosted API.
The example of integration can be seen here:
https://github.com/adammhaile/Elpis/blob/master/Elpis/WebInterface.cs
If you are using Windows Azure Web Sites for deployment (not Cloud Services) and developing an ASP.net Web Forms application, is it possible to use a 3rd party HTML to PDF converter? I'm starting to think I must convert to a Web Application instead of being a Web Form. I'm kind of new to all of this, so I'd appreciate anyone's input.
If by chance there are 3rd party HTML to PDF converters that are compatible with Web Forms and Azure Web sites, that would be useful. I'm rather happy with the site as-is, but I need to add in the ability to generate a PDF report and I don't fancy tearing up the code if I can avoid it.
Thanks.
Subsequent to my comment 27-dec I had to find a solution and 8 cents per document wasn't an option for thousands of documents. Eventually we build our own solution service http://www.html2pdfrocket.com and made it free.
We pretty much ended up doing exactly what you said - hosting it on Microsoft Azure Cloud Services - as you also discovered the Azure websites didn't have the flexibility or scalability to do what we needed but their cloud services is perfect for it.
I have an existing ASP.NET web application that I'm converting to MVC 1.0. The site started out with one goal. However, over time our sponsors are asking for more functionality and it is obvious that MVC would be our best route due to the new requirements. I've dabbled in MVC over the last couple of months and have a pretty good grasp on it all works. The problem that I'm faced with now is that the meat of our existing web application makes extensive use of a 3rd party tool that only works within ASP.NET WebForms.
The solution that I'm working on is to have two web applications running on the server. The one application would be our existing WebForms app and is solely used to expose the above mentioned 3rd party tool's functionality. The other application will be our main portal that will act as the new site. When the user wishes to interact with the 3rd party tool, I want to be able to load an iFrame on the appropriate Views that links the user to the other application and will then allow them to interact with the WebForms site. Does this sound crazy?
The number 1 problem that I'm faced with right now is how to configure my solution make the MVC application talk to the WebForms application. Every time I run the solution, a different port number is assigned to the two applications and I can't figure out how to configure my iFrame "src" properties correctly. Of course, I can't add the WebForms application to my MVC applictions' References, so I'm stumped!
Any help would be greatly appreciated...
If the port issue is the only problem, you can run both of them in IIS under a fixed virtual application.
But the ASP.NET development server also has the feature to fix the port to a specific number and not randomize it each time.