Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
There is swagger and there is nswag.
NSwag does some client generation.
Is it possible to generate client and display it as a link on Swagger UI for the consumers to download and use it?
Almost certainly not out the box. But then... you don't necessarily know what technology your client will choose. NSwag will generate a number of different types of clients in just a few minutes with little more effort than pointing it at the JSON Swagger definition (which Swagger/Swashbuckle automatically produces for your API), and is free to download; why not just let them do it?
You could speculatively generate a C# client for them and host it on your API server and serve it as say a zip file, but I don't really see the point, plus you'd have to make various customisation decisions for them, that they might prefer to make for themselves (namespace, HttpClient injection, partial class usage, etc).
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I created a http server using C# and I took the idea from here
It works with html pages. I tried to add aspx mime-type like this "text/aspx"
but it doesn't work, it's still opened like a text file!
Any ideas?
I assume that you have only implemented static resource handling for your web server. However, for ASP(X) (or any other dynamic content) to work as expected, you need a complex pipeline which loads the file, compiles it, runs the code in the right context, and returns the result (and that is a very simplified explanation).
In general, it's no a wise idea to implement your own server stack. You'll very likely end up with a vulnerable and badly performing piece of software. Just use an existing web server (or maybe even just Cassini if you really want to see the internals working).
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I have an ASMX web service which is internally calling some Payment related APIs and is currently processing few thousand orders daily. We are planning to upgrade this wrapper service to Asp.Net Web APIs. How can I explain the business the benefits of this upgrade in a non technical way as they might not be able to understand the technical terms? Budget and resources is not an issue for this upgrade.
Web API is better because it is based on HTTP and not SOAP. HTTP contains headers that give information on the content. It is more easier to understand and develop for. Since Web API is in HTTP it means that you are able to reach many more clients. The body of a http message can contain any kind of content.
From a business perspective it is easier to maintain, easier to develop and you are able to reach more clients. It also means that you are able to always extend functionality. With those qualities such as the maintainability and the ease of development means that it is ultimately cheaper and more effective.
In software whatever is easy to maintain and understand is the ultimate king from all angles (financial and technological).
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I work for a small Point of Sale Company, and we are working on a in-house tool to make our lives easier when it comes to ticketing and troubleshooting. Part of my task in this tool is to write a 'softphone' in C# WPF that we can use to accept incoming and make ongoing calls with.
We currently use OnSIP as our SIP provider, and are looking to build custom software to essentially allow us to auto-generate support tickets based on the phone number of the incoming call. In addition we will need call transferring, recording, hold/wait, etc.
The question that seems to be causing me the most trouble is really where to begin on something like this. Thoughts?
I'm presuming this is a desktop application?
Lookup pjsip.org, it's a portable C library which is very well proven. It will allow you to do all that you are asking, although it'll take you some time to write the wrapper code - you can find examples on the internet, however we have written a wrapper ourselves which I'll check on as we had intended open sourcing it. This is because when we did this last year, the examples just didn't work too well :-)
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I want to test my asp.net web api REST service that hosted in a HP-580dl and I want to measure the performance and response time when 10,000 simultaneous requests hit the service.
is there any way to do that in C# ?
Siege is a good tool for measuring load under concurrent requests: http://www.joedog.org/siege-home/
It's not written in C#, but there's no reason why it should be.
The Visual Studio load testing tools provide this functionality, and can control multiple agents in cases where you want a distributed profile and/or a greater concurrency level than a single client machine can support.
Create and run a load test
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
We want to implement a application help and documentation system. It should be based on HTML, because there are a lot of existing files and it gives us the most flexibility. Currently we use CHM files. We want to enable internal people (not developers) to edit the contents.
We thought of a stand-alone application that supports TOC, indexing (tags), search, etc. We also thought of using a local web server.
Until now our application uses pure C#, it would be good to keep this.
We are totally clean of web/asp knowledge, so the question is:
Where is a good place to start?
You can use documentation apps like SandCastle
Which use your XML documentation in your code to generate a help file.
Finally we ended up implementing a local HTTP server:
Internal people creates HTML content within our internal network
Our own build-tool creates the TOC and a search index and packs all content to a zipped file
The zipped file is packed into the application installation
When the end-user call help from within our application, the local http server is started
The HTTP server uses the HttpListener class
With this, it is possible to have some HTTP queries for special tasks like starting tools of our application by clicking a link without interception of the browser