after login,we get a white screen with no contents at all. The brower just shows a white screen.
Do a 'ViewSource' and see what's in it. If there is nothing, then your server has not returned anything as an HTML to be displayed. You need to look at the implementation, error logs and see if you find anything wrong. Response is not as you are expecting after login.
I have an asp.net application which is trying to consume a web service developped by using some language but from IBM environment. When I asked about wsdl location they gave me physical path rather than virtual path. If they would have given me the virtual path I could have used web references. But they have given only physical path. Which we can't access with web/service reference in our visual studio.
I have been given the WSDL file then I have we created proxy file using SOAPUI utility (SOAP-UI creates proxy for .net 2.o environment). Is it because of that or something else but I am getting exception when I trying to hit the service and get the data. It is giving me following exception.
The request failed with HTTP status 404: Not Found.
And in the stack trace:
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object parameters)
at WA.LNI.StayatWork.Public.UI.RetroMembersV1WSDLService.RetroMembersV1WSDLSOAP_HTTP_Service.GetRetroMemberInfo(t_request request) in D:\source\SourceCode\StayatWork-VS2010\WA.LNI.StayatWork.Public.UI\RetroMembersV1WSDLSOAP_HTTP_Service.vb:line 48
at WA.LNI.StayatWork.Public.UI.WebServiceTestPage.Page_Load(Object sender, EventArgs e) in D:\source\SourceCode\StayatWork-VS2010\WA.LNI.StayatWork.Public.UI\WebServiceTestPage.aspx.vb:line 184
And one more thing to add now I found that my application call even not going to the proxy class. Because I put break points in my proxy class contructor and few other methods, my application is not even going to those break points whats this weird thing I dont know. Please anybody pls help me its little urgent.
Well that's an oxy-moron, asking for help accessing a web service, but you can't even get to the web service, so the web service has nothing to do with your problem, because your not even there yet.
So I'm looking at a stack trace for no reason here.
404 means the HTTP request could not be made, the rest of the trace says it sent the request, but no response was delivered. So the request went somewhere on port 80, or else it would of stalled for a very long time with a page not found error. if no port 80 was there, it would be an instant return.
I could able to hit the break point, I was not hitting break point becuase System.Diagnostics.DebuggerStepThroughAttribute() attribute was set on my class. But still I am getting the same exception.
And as you said its returning immediately.
I am not finding the reason please help me its an urgent.
hello urgently i am fresher plz............ my question is that how can see different different content in div on same page after click on menu.
example --- we take a tab(service) on menu bar in dropdown form such as service---- |---security device |--- event management |--- property dealing when i click on secutiy device then it only open the detail of secutiy detail on same page(service).similarly in case of event management, property dealing. on particular id.
I am mostly focused on DB and desktop development, all of my "good" web stuff was done with WebForms. As my spare time allows I am slowly learning ASP.Net MVC, I agree with philosophy behind it, but learning process is much slower than expected and from time to time I look across the fence for possible shortcuts, alternatives etc.
So, should Web Pages be considered as an alternative (of any sort) to ASP.Net MVC?
Do you consider it better than WebForms (and why)?
Are there any important gotchas which usually aren't listed among first N Google results?
Can someone share their experience?
I have worked on Webforms previously and now MVC. In my opinion MVC is better in performance, speed and flexible for test-driven development. Here is the interesting part.... No postbacks, No viewstates, No server controls, No page life-cycle. All done with HTTP RESTful services and HTML controls. And it's completely stateless. Controller controls all user interactions. each user request is served by raising an action method in the controller. Bundling, routing and Web API's are some of the interesting areas in ASP.NET MVC