I'm trying some WCF ajax.net 3.5 out for the first time, and I'm having some difficulties. I have a WCF Service which I have connected to in my aspx page using <asp:ScriptManager>. I have a custom object which has been decorated as a [DataContract]. I'm calling the object from javascript successfully, I can see the JSON response in FireBug, but Sys.Serialization.JavaScriptSerializer.deserialize() chokes on it. I'm sure I'm making a noob mistake, but I used up all my patience getting the Web.Config values right for running the WCF service.
I have a class that contains an enum property, and upon serializing the object using JavaScriptSerializer, my json result contains the integer value of the enumeration rather than its string "name". Is there a way to get the enum as a string in my json without having to create a custom JavaScriptConverter? Perhaps there's an attribute that I could decorate the enum definition, or object property, with?As an example:
I am using .Net Framework 3.5 on an ASP.net web project using jquery.ajax to make web service calls. My web service returns objects serialized as JSON by specifying the content type of my POST as "application/json". I would like just one of my many properties to return a non quoted javascript function name instead of a quoted string. Serialized as such:
{"dataInit": functionName, "id": "myID"} instead of {"dataInit": "functionName", "id":"myID"}
I want to use the DataContractJsonSerializer class. This is contained within theSystem.Runtime.Serialization.Json namespace and the System.ServiceModel.Web dll.or some reason, when I add the using directive for the namespace, Visual Studio says it doesn't recognise the Json namespace in System.Runtime.Serialization.When I try to add the System.ServiceModel dll, nothing happens, which suggests to me it's already referenced. (Because nothing also happens when I try to add a reference to System.Web which is definitely referenced!)
I'm getting the error from the subject line when I try to move some code that formerly lived in the App_Code directory to an external library (that would be moved into the /bin directory). What do I need to include or reference to get rid of this error?
I've already included: System.Runtim.Serialization (says it's version 3.0.0, I don't see a version 3.5.0 anywhere).
I am trying to return some data as json from an action method.
I have an employee object that looks like this:
public class Employee { public int EmployeeID {get; set;} public string FirstName {get; set;} public string LastName {get; set;} //Other irrelevant properties }
Then I have a view model as follows
public Class EmployeeViewModel { public Employee Supervisor{get; set;} public List<EmployeeViewModel> Employees }
I need to return a json object that looks exactly like this:
For now I only need to go to the second level as above, returning and supervisor and their staff members beneath them.
How would I go about returning this in my action method(I have the viewModel object hydrated already I just need to return it as json). My problem so far has been that the children property does not get populated.
I have a text file named gisQuery129.json that is created using Json.NET - [URL] There is an example on how to create a JSON file and I have done that successfully, but I want to read the file on a page load event and add the values to .NET textbox controls for input values in a query. The created file looks like the following:
{ "myData": { "randomNumber": "129", "Application": "MyMapApp", "FeatureId": "ALL", "Feature": "ALL", "spatialQuery": "FEATURE_ID= '11111' AND REQ_SEQ_NUM= 1 AND RAND_PARAM= 129 OR FEATURE_ID= '22222' AND REQ_SEQ_NUM= 2 AND RAND_PARAM= 129" } }
I want to read the data in the above sample JSON data and then populate my textboxes something like this:
txtRandParam.text = "129" txtApplication.text = "MyMapApp" and three more text boxes after that.
I use the JavaScriptSerializer class of ASP.net to serialize my object and return it to the client side. How can I deserialize the string using JavaScript?
I've been tasked with implementing a JSON feed on an asp.net website that will be consumed by 3rd party apps (such as IPhone, Android, etc) and I'd like to follow best practices.
An example of what I'd like to achieve would be something similar to: [URL]
I've chosen the JSON.net api as this seems to be highly recommended.
My Google-fu must be failing me as I can't find a single full example code for an Asp.net web application with JSON.net implemented on it, so I've no real concept of where to begin.
My question is fairly simple:
Should I create this sort of feed as an ASPX, or ASHX file? Or even a .NET Web Service? (Remember that the tools that will be using this feed are on external apps like IPhones, etc)
I created a test feed in both ASHX and ASPX format ... here is the code (I'm using Subsonic to populate the collection) ... are either of these along the correct lines?
I am using business objects that are accessed via webservices. These objects can be loaded via the webservice and serialized to my mvc app. The mvc app can get a web reference to the objects and they can be utilized in the mvc app. However, the business objects are where the classes are defined, and where the annotations are applied.
The mvc validation seems to have no idea that there are System.ComponentModel.DataAnnotations attributes applied to this business object class.
1) Are DataAnnotations lost when objects are serialized / deserialized?
2) If in mvc I use a view model approach, and have nested objects (which themselves have public properties - decorated with DataAnnotations) can/will the mvc validation system traverse the entire object model, the model being used for my view? (so it can see DataAnnotations attributes of the nested object)?
I had an interview Thursday and one questions that I was asked in the technical interview was a little confusing.
First, he asked me about Viewstate and I explained to him what all that entailed.
He then asked me what happens if the data you are putting into the Viewstate gets to big.
I told him you could then use Sessions or start storing things in the Database.
He said, what about Data Compression? I immediately responded by saying, yes you can use Serialization/Deserialization to store/retrieve the data (i'm using that in my open source project).
When he says "Data Compression", is he talking about "Serialization" or is this something different?
Code: public class GroupInfo { private List<Structure> _sectors = new List<Structure>(); [XmlElement("Sector")] public List<Structure> Sectors { get; set; } [XmlElement("Person")] public List<Users> Person { get; set; } [code]...
I want users to be able to export data as an XML file. Of course I want them to be able to later on import that same XML file however they always could change it or it could be a different XML file. So I want to validate the XML file to check if it is in the format that I expect. So I guess I would need something like a schema to check just that it has to be through code. So if I expect
I don't want some other format to be in the file other then the one I expect. Also how would I validate fields? Like say I require that there must be some text in between tags. If it is blank the file is not valid. So how could I do this?
I decided to use XML serialization so I know it will through an exception if it is the wrong format and ignore stuff that does not work. However I am not sure should I just go through it and C# to validate each of the records or should I try to make an xml schema to do it. If I would want to do it through an xml schema with xml serialization how would that work? Like Do I first do something like I seen in the responses then de serialize it? Or how would I do it?
I follow the code snippet to calculate Session size. Profile Memory Usage of Session State ASP.Net My problem is some properties of objects aren't marked as Serializable so I cannot apply the solution. Can I just bypass non-serializable properties?
I am having a lot of trouble with WCF web service over SSL / HTTPS, so I was wondering if (as a quick fix) I could serialize the object, convert that to a byte array, encrypt the array, pass the encrypted array.
On the other side receive the encrypted array, decrypt the array, convert from the array and then deserialize the object.