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 4 years ago.
Improve this question
It is about the efficiency, which chrome being light weight, fine for general web browsing.
I am thinking to use it as default browser when working on Web Applications. There are some limitation though which I know like, Could not use chrome when worked over an Rss Feed generator module, as chrome was not supporting the generated output.
Which browser will make it a good combination with VS 2008, C#, Asp.Net dev Server for developing Asp.Net Web Applications.
(Not concerned about the User Interface, Layouts, presentation CSS or same. It is about checking business logic implementation or serve rside testing, when we check behaviour not presentation. It is when we have to kick debugger into action every other minute to see how application / module / class / statement, whatever is behaving like, but not how application looks )
Firefox + Firebug is truly a deadly combo.
As for the performance problems with ASP development server, try the following:
go to about:config (write it into the address bar)
change the value of the network.dns.disableIPv6 property to true
A web developer with only one browser is like a cook with only one knife. You could always try everything you do as a web application on many different browsers. Some things may not work or may not look like you expect.
I like to use Firefox and Firebug when debugging client-side javascript issues, and I sometimes use Firefox to ensure the app works in that browser too (we require FireFox and IE support) so on one level you will need multiple browsers to validate the web site works in all of them to reach a wider audience.
I like to use IE so I can use the in-built debugging capabilities (inside VS), which you don't get with the other browsers. I like to use Firefox for the client-side JS errors that I may encounter.
I've had issues with Firefox and the visual studio dev server.
It works fine, but it's slow for no apparent reason.
When I'm more concerned with server-side debugging, I tend to use IE simply because it loads the pages faster.
Once you're working on client-side testing/debugging though, you should definitely be working with a variety of browsers. I start with Firefox just because I love the Firebug addon more than I probably should!
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 7 years ago.
Improve this question
Say I coded some application in C# using visual studio. Is there anyway I can take this application and embed it into a website so folks can use it from a website in the same way I would use it from my desktop?
If you coded a console application - no.
If you coded a winforms application - no.
If you coded a WPF application - yes
Two options:
Migrate it to silver light and it will only work on browsers which can install the silver light plug in. keep in mind that silver light is being disbanded by Microsoft, so it is not considered a recommended practice anymore even by MS. also consider that not everyone would agree to install silver light plugin for their browser.
You can also migrate your WPF to become a browser application - but this will require the client machine to have .Net installed on it - so this is like a replacement solution to what once was achieved by ActiveX technology.
Main difference between those two options is that the 1st one is cross-platform/cross-browser solution and the 2nd one is not.. however this might change in the future as .net is becoming available to Linux too..
If you coded ASP.Net - it is already designed for developing web applications.
I'm not sure what exactly you are trying to achieve but I think the WPF/Browser APP is what you looking for, you can read more about it in How to: Create a New WPF Browser Application Project
Edit:
I thought I'd mention if you have a Console or Winform app that people wish to use remotely (ie via a web browser) don't forget they can use Remote Desktop to access the application. Many large enterprises do this using Citrix. Often this is more practical when the cost of rewriting legacy applications is not feasible.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 8 years ago.
Improve this question
I have a scenario I need to avoid my ASP.Net web application should not run in Firefox. If any one tries to open my application it will redirect to Chrome or Internet Explorer. I don't know how achieve this
situation.
Is it possible to handle this using JQuery or JavaScript ?
Simple answer: No
Longer answer...
Your question is fundamentally flawed - you simply cannot make a browser on a computer open a different browser on the same computer.
If you could to that, it would be a massive security flaw... and that is why you can't.
Although I don't like saying it - you could write an OCX (active X control) that would probably allow you to do it... but that would only work in Internet Explorer - and would require the user to install it.
But as you want to move from FireFox, this obviously doesn't answer your question.
No. It is not possible. You can't force a browser to open another application on the client machine (beside some browser plugins, like Adobe PDF).
Think what would happen if I could open your bank's application though javascript.
Everything is possible in technical sense. But if you try to do this way you may invite unnecessary issues from other browsers and loose focus on main objective.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
I'm developing a web crawler in .Net C# that works like this.
Step1 Visits main page of the site (let's call this page Main.aspx)
Step2 Use httpwebrequest to get the form page (Let's call this page Form.aspx)
Step3 Post the form to another page and get the results. (Let's call this page Results.aspx)
It's pretty straight forward in terms of web crawling.
The current problem is, I can't access Form.aspx page if I dont set a bunch of cookies before. All of these cookies are javascript generated by Main.aspx.
Whenever i try to directly get the Form.aspx page, i get redirected to the Main page. The code that generates the cookies have more than 20kb and its aboslutelly messy and insane, also it uses a lot of "document." references which would block a simple attempt to use JINT or Javascript.net
So after a lot of research i found out that a headless browser would be what I'm looking for, tried a lot of them, but it seems a lot of complication. I already have a class library project with all my web crawlers in there, i just wanted another dll to make it work. Any suggestions?
I'm trying to be as clear as possible, if you have any doubt, please post on comments before giving negative votes...
Use a .NET binding for PhantomJS, which is a headless webkit browser. You might consider going to a full-blown automation framework like Selenium, which is made for testing.
What you are asking for in not simple, though. You are asking for a lot of abstractions so that you can keep the amount of simplicity in your app that you have now.
If you didn't mind a "head-ful" browser, you could also use the Windows Forms "WebBrowser" control or remote control Internet Explorer through COM.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
I am (was) a Python developer who is building a GUI web scraping application. Recently I've decided to migrate to .NET framework and write the same application in C# (this decision wasn't mine).
In Python, I've used the Mechanize library. However, I can't seem to find anything similar in .NET. What I need is a browser that will run in a headless mode, which has the ability to fill out forms, submit them, etc. JavaScript parser is not a must, but it would be quite useful.
There are some options:
WebKit.Net (free)
Awesomium
It is based on Chrome/WebKit and works like a charm.
There is a free license available but also a commercial one and if need be you can buy the source code :-)
HTML Agility Pack (free) (An HTML Parser library, NOT a headless browser)
This helps with extracting information from HTML etc. and might be useful in your case (possibly in combination with HttpWebRequest)
More solutions:
PhantomJS - full featured headless web
browser. Often used in pair with Selenium which allows you to
access the browser from .NET application.
Optimus (nuget package)- lightweight headless web browser. It's in beta but it is sufficient for some cases.
I used to use both for web testing. But they are also suitable for web scraping.
You may be after TrifleJS (currently in beta), or something similar using the .NET WebBrowser class which communicates with IE via a windowless ActiveX/COM API.
You'll essentially be running a fully fledged browser (not a http request wrapper) using Internet Explorer's Trident engine, if you are not interested in the JavaScript API (a port of phantomjs) you may still be able to use some of the C# codebase to get around key concepts (custom headers, cookies, script execution, screenshot rendering etc).
Note that this can also emulate different versions of IE depending on what you have installed.
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 have an asp.net web page with a "dial" button; when the user presses the button, it connects the user to the PTSN network to make a phone call. This is for outbound calling only so there's no need to worry about incoming calls.
I'm thinking of using a webphone and finding a VOIP wholesale provider. Ideally, I'd like the server that's hosting the web app to not be involved in this process (ie. the webphone connects directly to the VOIP provider).
What are some of the pitfalls to avoid?
Thanks for your suggestions.
There are a few Flash based softphones around you could use. I'd recommend taking a look at Phono from Tropo. It's designed for initiating calls via javascript in the browser. I think it does or will use HTML5 where available but falls back to Flash for some parts.
One pitfall: WHat you describe is not a web page, it is a local application the user has to install ON HIS COMPUTER. Mileage may wary.
ASP.NET is not running on the users side (beginner mistake). It is a server side technology - the user basicall gets normal HTML, Javascript... which has NO higher programming capabilities and no voip capabilities. Lize a pizza delivery - asp.net is the top oven, but the user gets a normal pizza. Point.
So, your pitfall is that you need to make a web call out of a HTML page (no asp.net involved, no .net involved) and this is not possible without the user installing software on his computer.
SOmething like FLASH may work, or silverlight. But I expect some rights issues (especially: connect to ANOTHER server, not the server hthe flash / silverlight plug in was loaded from) which require configuration / epriviledge elevation, i.e. no normal users again.