The required dll in order to run WebInput successfully using SmartWebResources is:

• ISNet.WebUI.WebInput.Resources.dl
• ISNet.WebUI.WebInput.dll
• ISNet.WebUI.Resources.dll
• ISNet.WebUI.dll
• ISNet.dll

I have verified All the required dlls have the correct versions.

The following are run from the GAC and have an assembly reference in the web.config just like the WebInputSamples.  Meaning, if they were the problem, the Samples would have the same problem.

- ISNet.WebUI.dll
- ISNet.dll

Since I can run WebGrid and WebCombo, if there was a problem with the framework being out of sync, they would probably be having the same problem.

I am guessing the the URL for the .js, in the error details, 307200216 indicates the version.

The code that errors "if (v74f99.DynamicEditFormat.MaskInfo)" , the 3rd line below:

if (v74f99)
{
	if (v74f99.DynamicEditFormat.MaskInfo)
	{
		if (!v74f99.DynamicEditFormat.IsValidateOnChange)
			return true;
	}
	else
		return false;
}

v74f99.DynamicEditFormat is undefined. It did not even check before trying to access the MaskInfo Propery.

1. Where does DynamicEditFormat come from?

- Do I need to manually assign something via a control property?

--- If so, even the Wizard does not do this.

- Is this created automatically?

--- If so where?  Maybe that is where the problem is

2. What is v74f99?

3. What inhibits the user from typing alpha characters?

--- Is this an event or behavior?

4. What is ClientBehaviour.js for?

--- I see it in the IIS log but it is like it is not hooked up to the controls, hence that is why things are not formated as I type?

All the .js in \Program Files\Intersoft Solutions\WebUI Studio\CommonLibrary\WebInput\V3_0_7200 have a timestamp of 10/22/2009 and an interanl header 10/23/2009.

My colleague, Yudhi, has been corresponding with you for this issue. It seems the issue occurs only in a very specific project. We also have consulted our developer regarding this issue. In order to solve this issue quickly, do you mind preparing a simple project which has the issue described above? In our environment we are having difficulty replicating this issue.

Regarding the v74f99 variable, I could not give you any information regarding the variable since it has been ophuscated.

The ClientBehaviour.js is used some WebInput client side functionality especially for highligting character, word, or sentence.

Hi Glenn,

You did not answer all the questions.

1. Where does DynamicEditFormat come from?

- Do I need to manually assign something via a control property?

--- If so, even the Wizard does not do this.

- Is this created automatically?

--- If so where?  Maybe that is where the problem is

----- What if MaskInfo is not specified in the Control

2. What is v74f99?

I know it is obfuscated.  It is simple, don't search obfuscated code, not the source.

Just look search the source code, DynamicMaskValidator.js, for "DynamicEditFormat.IsValidateOnChange".  That will narrow down where the code occurs.

Then look for creates of DynamicEditFormat in all all the source.  Don't tell me no one there has a clue.

Or, give me the Source and I will do it.

3. What inhibits the user from typing alpha characters?

--- Is this an event or behavior?

4. What is ClientBehaviour.js for?

--- I see it in the IIS log but it is like it is not hooked up to the controls, hence that is why things are not formated as I type?

NEW QUESTION:

5. What code replaces the alpha characters while typing?

6. What code formats the input to currency?

7. Once you find 5. & 6., what code hooks up these events?

--- This way we can concentrate on why it is not doing it's job.

As for a Simple Project, it will not be simple

-- You have to setup up Forms & Authentication to start with.

-- It will takes me days to provide you with a Simple Project.

So while you wait for me, please answer my questions.

This problem can also be solved by working it forward with the clues we have and without waiting for it to be worked backwards with a very time consuming Scaled Down, not Simple, Project.

There appears to be a conflict with something in my Project since you have verified all assemblies are in place. 

The only info I could share is this issue occurs because the DynamicEditFormat is null. In this case this object should not be null. We also have found out the culprit of this issue is in the rendering of WebInput in your project (the page has been supplied through email), the markup rendered in you project is:

<xml id="WebInput5$mv_x"><!--[CDATA[<MaskValidator Format="c" MaskType="DynamicNumber" Enabled="True" IsValidateOnChange="True"><MaskInfo REExpression="^$" ArrLiterals="" ArrLiteralsChar="" MaskExpression="" PromptChar="_"><ArrREExpression /></MaskInfo><WindowInfo IsEnabled="True" ControlID="WebInput5$mv" DisplayPosition="Right" DisplayType="Normal" OffsetControlID="WebInput5_f"><OffsetLocation /></WindowInfo></MaskValidator>]]--></xml>

The separator should be _ not $. This issue has occured before in previous build of WebInput. Our developer suspect your project still does not reference the latest WebInput. We also could not replicate the issue using the latest WebInput build.

Hi,

My Testing showed that DynamicEditFormat is checked in  DynamicMaskValidator.js.DynamicMaskValidatorEvaluateIsValid().  It also showed it should not be called.  Hence, it does matter that it is null.

More importantly is, why is DynamicMaskValidator.js.DynamicMaskValidatorEvaluateIsValid() being called?

Then, am I correctly assuming:

- QUESTION 8: The ControlID Separator of Dollar Sign is what is causing CoreValidator.js.EscapeRegExpSpecialChar() not be called?

- QUESTION 9: ISNet.WebUI.WebInput.dll creates the ControlID and Version 216 does not use a Dollar Sign Separator, it uses an Underscore?

Additionally: 

- QUESTION 10: What Version did ISNet.WebUI.WebInput.dll start using a Dollar Sign Separator?

- QUESTION 11: Could you replicate the problem using the Version of ISNet.WebUI.WebInput.dll that uses a Dollar Sign Separator?

I have spent over 3 hours with Yudi and at least as many on my own verifying version numbers and re-referencing WebInput.  Maybe it is a different assembly.

NOTE: Would you please refer to the Question Number when responding.  It is difficult to determine if you are answering my Questions.

Through email correspondence & sharedview session the issue culprit has been confirmed, the issue is caused by the <xhtmlConformance mode="Legacy"/> in the web.config.

An article regarding this property has been provided in here, this should answer the question about the $ sign separator.