Cookies are one of the many options available for state management in ASP.NET. A cookie is a small file on a client file-system that can be stored or retrieved from a browser session. These can be used for many things, but frequently are used to maintain a user session after the browser has closed – this comes into play with those “Remember Me?” checkboxes on log-in screens. When a user checks the box, they are usually consenting to have a cookie placed on their system.
You are here
Recently, I was working on a solution which required a scheduled download of a hosted file. There are a few samples floating around online of how to do an FTP download/upload, but I figured I would share what I've been using as it is incredibly simple and does the job perfectly.
We utilize WebClient and NetworkCredential, so the System.Net namespace is required. Then, we just supply credentials and call either the DownloadFile() or UploadFile() method which require the source and destination folders - that's it! Below are examples of each.
WebForms in ADX studio provide a powerful tool to create and manipulate an entity record on the portal in multiple steps. We can choose to stick to the out of the box step types that perform standard operations, such as displaying CRM forms, redirects or conditional branching. We can also wire in steps that execute custom user controls that we added to our ADX .NET solution. All of those tools give us a wide set of options to model interconnected processes within one single WebForm.
Recently, in Dynamics CRM, we were coming across some issues with the processing of async services (specifically plugins). The environment was pretty robust, but we had a lot of processes going on, and we would frequently see the async services max out what memory we had available on the server, which required a restart of the services (not ideal).
ADX Studio provides a powerful way to display CRM forms and orchestrate multi-step web flows on the web. A web flow step can be configured to display a particular CRM form on the CRM level. Unfortunately, this happens on the CRM level of the ADX portal configuration, which hardcodes a certain form to a step.
We recently had a need to be able to retrieve picklist values from the Salesforce case entity for use in another web application that was built using .NET. There are several ways we could have accomplished this. The first would have been to manually add the items to the other application (either hard coded or stored in a database). The problem with that approach is keeping the values in sync becomes troublesome. Do you have someone manually updating items as they change? You could, but what if they forget to update the external application?
WCF Data Services has been around for some time. It’s the .NET programming framework for building OData services. I’ve used OData a bit with Dynamics CRM in the past, but it wasn’t until recently when I leverage WCF Data Services that I really appreciated its ease of use.
The Qlik Sense APIs are the same APIs we use to develop Qlik Sense itself. This gives you tremendous flexibility to build, extend and combine Qlik Sense with other technologies. With the Qlik Sense APIs you can:
- Integrate Qlik Sense into web or .NET applications
- Extend Qlik Sense by adding your own visualizations and your own data sources
- Manage licensing, users and Qlik Sense server tasks programmatically
Even though JSON is more frequently used for data interchange now, I still find myself dealing with the serialization and de-serialization of XML data from time to time. In .NET, building the classes to support the XML structure can be time consuming and tedious for complex data.