This is a sample application that I worked on that utilizes simple forms authentication to authenticate a 3rd party .NET application (in this case an ASP / C# solution) through the iMIS Public View. This method essentially sets Public Views as the authentication source in the web.config file so if the session is not set, it goes to Public Views and once a user logs in successfully, it passes the cookie information back to the sample application. Once the session expires, it goes through the entire process again. I see this as the simplest way to maintain iMIS as the a single login source for 3rd party web applications. Keep in mind that this only returns the unique Web Login value from iMIS so the appropriate table such as name_security or usermain will need to be queried to get the actual iMIS ID but that is something that is easy to do. Of course more elegant methods such as SOA are out there but I figured this is a good place to start especially for the smaller projects.
Frequently, customers have a previous website where they have logins and passwords they would like to preserve in a new iMIS based website.
The following is sample Coldfusion code on how to access the new i15 MembershipWebService and user the RegisterWebUser method to load logins and passwords into iMIS in bulk.
This can also be modifled to replace the Generate Logins functionality of e-SEries by pre assigning logins and passwords based on a formula.
Attached is a document with specifics on how to use the iMIS15 MembershipWebService to login a user from a third party site.
Please comment with any errors, omissions or additions you may have.
80% of the development of this process was done with the help of Eric Means.
These are the TFS rules that Microsoft turns on for their development.
I am writing a custom asp.net application in C# for a client in Brisbane (REIQ). This application is integrated into iMIS and will be accessed from the Certification module.
One of the pages has a datagrid which has a hyperlink column. When you click on the link on this column, it should take you to that event registration.
The URL I am using is:
I've just uploaded the source code and demo videos for the iMIS Mobile application that I demoed at the Innovations conference.
I've also setup a live site that anyone can play with using a mobile browser. See it in action here:
There are tons of devices out there, and I only have a few that I can get my hands on personally. So, let me know how it looks on your device!
Microsoft have just announced that Expression Web and Expression Blend will now be available at no extra charge to all MSDN Premium Subscribers (this includes customers with the "VS Professional with MSDN Premium" subscription). This means many more developers will have these design tools for building ASP.NET, WPF and "WPF/E" solutions.
Before Christmas I attended a Microsoft presentation on LINQ. Attached are the screenshots and notes from the talk.
Microsoft describes LINQ as "The LINQ Project is a codename for a set of extensions to the .NET Framework that encompass language-integrated query, set, and transform operations. It extends C# and Visual Basic with native language syntax for queries and provides class libraries to take advantage of these capabilities."
Over the last 18 months or so as we have deployed the iMIS .NET server at clients and then tried to roll out components like IQA, etc to certain users, we (sorry, I wiped out the authors name accidentally) have experienced a variety of environment-related problems to which we have employed a variety of environment-related solutions. I was hoping that somewhere there existed or we could create (here perhaps) a definitive list of things to investigate / try when the rather inexpressive iMIS .NET error page pops up.
A few of us went to a Microsoft presentation at Cambridge University last night on ASP.NET and AJAX (aka Atlas). It is currently on Beta 2 and should ship by the end of the year.
The presenter recommended taking a look at Scott Guthrie's Blog on ASP.NET and .NET:
There is a lot of interesting stuff there.
Scott is the General Manager within the Microsoft Developer Division. He runs the development teams that build the following products/technologies: