I’ve added a page to IC for recording details of release schedules for software used by iMIS – for example the next versions of Microsoft SQL Server or Microsoft Office.
http://www.imiscommunity.com/microsoft_and_other_vendor_software_release...
If you come across any information on release schedules for products that we use or integrate with can you update it here.
I just passed my first in the Microsoft .NET Framework 2.0 series of exams, MCTS 70-528 "Microsoft .NET Framework 2.0 Web-Based Client Develoment". This is one of the two tests required for MCTS .NET Framework 2.0 Web Applications certification. The other test required for this cert is MCTS 70-536 "Microsoft .NET Framework 2.0 Application Development Foundation", which I'm planning to take sometime soon.
Symptom: If you're seeing random, periodic extremely slow page refreshes on your iMIS app server (full or public view, either one), check the first section of this Howto for the ASP.Net "idle worker process timeout" setting.
The issue is that by default, IIS kills the ASP.Net worker process after 20 minutes of inactivity, causing the next page access to restart the appdomain (leading to that annoying "first hit" slowdown as all the business objects are loaded, iBO initialized, etc).
Hi all,
I was wondering if there is an option to enable E-mail redirecting to a single account to prevent Customers in the database from receiving test E-mails?
Thanks.
In the days of client/server applications the amount of data sent “over the wire” was not typically a huge concern unless the data was very big. This is because client/server applications typically run on local networks with 10, 100 or even 1000 Mbps connections; plenty of speed for most data applications. In the web world, however, more people access their application over remote networks, like from remote offices, home, or Starbucks. These are typically much slower connections, have to go thru many routers along the way (called “hops”), and often travel thru VPNs which encrypt/decrypt the data along the way.
To create more than one instance of IMIS on a single server without using the multi-instance utility the following can be done.
1) Create the first instance and connect via the iMIS client and IMIS Public website to make sure that you can authenticate. The default installation location is the C:\Program Files\ASI directory.
2) Make a copy of the entire ASI directory and rename it to “ASI_SecondInstance” or another identifiable name. The path of the second instance is then C:\Program Files\ASI_SecondInstance. In this example ASI is the first instance and ASI_TAPA is the second instance. See the file system view in image one.
Here's how to get the Word Merge control working on Windows Vista/IIS7.
Much of the .Net code we ship (or will at some point ship) depends on sensitive values that are stored in web.config files. This sensitive information includes database usernames and passwords as well as application login names and passwords.
One way to protect this information is by using file permissions; obviously, if a user doesn't have read access to a .config file, they won't be able to open it and read the information. Unfortunately this isn't always practical.
I have been conceptually trying to figure out how to run an IQA through Adhoc in iMIS.
Why: So many functions can be achieved in this way, writing activities, mail merge, email merge, reporting... this are all lacking from IQA (by design i guess) right now. However IQA is a friendly interface for selecting records. Additionally we shoulnd't expect customers to have to write a set of criteria twice just becuase they want to do two different things with the same data, once in IQA and once in Adhoc.
