Has anyone worked with wCM long enough and have multiple site where the navigation is in folder structures and causing long URLs with duplicate folder names?  See below, the site name wcmdemo is listed once for the navigation and once for the content, can this be changed?  I have setup a second app server and single site in IIS to host it at a native URL without the need for the site name so that will help, but it still adds more to the URL then is necessary and will impact the nice clean URLs that wCM should have.

Not sure if we are going about this the right way but we are working on getting the iMIS 15.1 public view ready for production.  We've create a master page and template directory but so far when we change the web.config file to point to the new master page it reverts back to the Public.master file in sub pages.

We have tried to change the code in the events.aspx file from:

<%@ page language="c#" inherits="Asi.Bae.Web.Events.Events, Asi.iWC.Core.Events" 
	masterpagefile="~/Templates/MasterPages/public.master" 
	title="Events" enableEventValidation="false" %>

to:

There are several problems that have been becoming more prevalent with iMIS 10.x.NET and iMIS15 involving various security and connection issues. Below, is a list of common issues and solutions:

• 13: Type Mismatch Error when trying to log in through the desktop
• The login account 'sa' has been locked out
• The webpage is unavailable

These are becoming more common errors and are caused by several different possible problems:

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.

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.