c# - Visual Studio External references not working on published website -

-

I have created a web project that works fine when published and when debugging in Visual Studio. When I add an external reference through the reference manager, it connects it properly and runs within the internal IIS Express within Visual Studio. When I publish the website to my server, external apps do not work and it looks like they are not available.

What do I miss to see these interop DLLs in the web server?

There should be some 'hook' to connect with these DLLs which are run locally when it is not present when deployed. In essence, this is an API that I am trying to deploy on the server where the app is installed and running. The API works normally when localized VS is run inside, but when I put it on the IIS website on the same server, it does not work. There is full permission on the IIS website, which is not an issue because this site runs only on an internal network and not on the web.

UPDATE: Deep digging in the secret I suspect that something is done with the way COM interpaces, or APIs are used, I set property properties for 'COM interop' to generate And AOI reference properties are set to isolated = false and encrypted type type = true. I have also set Commonweb = true for the entire project. There are no errors in the .NET or IIS logs that I can see. I have set the full permissions for all applicable folders. So, what am I missing?

I think I have been stumped on this community. I'm going to try to replace a late collar and if he helps.

For those interested, this issue was with DCOM permissions on the server. Still does not work, but at least the server now sees the API, just COM exception errors but it is out of my capacity. There is no source code or vendor support for the API. Ever since I pay for APIs and when I ask for help, I say no help is available.

If you are referring to local external assemblies, add them as part of the solution ( Say in a third party accessories folder), and then set each DLL to "Always Copy" under properties.

It should be ensured that your assembly has been copied to your bin, and they will be visible on your web server.


Comments

Post a Comment

Popular posts from this blog

apache - 504 Gateway Time-out The server didn't respond in time. How to fix it? -

-
Using a form submission on an embedded iframe , the customer downloads a compressed log file Requested. The request was sent to the server, which is the compressed log files, perform some database operations and returns a compressed file. After just 2 minutes, 504 gateway time-out server did not respond timely message on browser net panel How to fix this error? The log files were taking a long time to compress, and timeout was set to 2min The error was fixed by extending the file file: # # timeout: The number of seconds before getting the time out. # # # Timeout 120 timeout 600
Read more

c# - .net WebSocket: CloseOutputAsync vs CloseAsync -

-
We have a working ASP.NET Web API REST service, which is one of the methods of our controller, HTTPTTEX. .) Socket handler code looks something like this ... Public async task socket handler (AspNetWebSocketContext context) {_webSocket = context.WebSocket; ... while (! Cts.IsCancellationRequested) {WebSocketReceiveResult Results = _webSocket.ReceiveAsync (Input Segment, cts.Token) .Result; WebSocketsStateCollusocketState = _webSocket.State; If (result.MessageType == WebSocketMessageType.Close || currentSocketState == WebSocketState.CloseReceived) {// What should I use. CloseAysnc () or. CloseOutputAsync ()? _webSocket.CloseOutputAsync (WebSocketCloseStatus.NormalClosure, "Client Requested", cts.Token). Wait (); } If (currentSocketState == WebSocketState.Open) {...}}} .What is the difference between .CooseAsync () and CloseOutputAysnc ()? I tried both of them and they both seemed to work fine but some difference should be the same they both describe very similar to...
Read more

c++ - How to properly scale qgroupbox title with stylesheet for high resolution display? -

-
I am trying to apply a stylesheet for QGroupBox (QT4.8), which works on the normal screen ( 96 dpi) high resolution screen (Yoga 2 Pro, 3200x1800, 275 dpi, windows 8.1). The following style looks good on the 275 dpi screen, but the top margins on a regular 96 dpi screen are far too big. QGroupBox {border: 1px solid red; Range radius: 7px; Margin-top: 12x; } QGroupBox :: Title {subcontrol-origin: margin; Subcontrol-position: left above; Padding-left: 10px; Padding-right: 10px; } Changing the top-margin has an effect, but I did not get a proper setting which works on both screens. If I shorten the value, the content of the group box overlaps with the title on 275 dpi screen. I was also playing with units "East", "PX", "MX", "PT". Reading the document I would have guessed, "2 X" was the correct solution, which should be scaled with different screen resolutions. Without the stylesheet, the groupbox works well on both screens. ...
Read more