Installation Error in windows XP with solution

Jun 27, 2012 at 9:33 AM
Edited Jul 1, 2012 at 11:18 AM

I tried to install the SageFrame source version in my system, my operating system is windows XP and VS 2010, IIS 6 with service pack 3 and dot net framework 3.5.But it did not get installed. When I tried to install from IIS, some error displayed as follows:

A name was started with an invalid character. Error processing resource 'http://localhost/SageFrame/'. Line 1, Position...

 

<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="SageFrame._Default"%>

-^

And if I tried to run the solution file, it gets stuck during installation.

I referred many forums like

http://forums.asp.net/t/887716.aspx/1?A+name+was+started+with+an+invalid+character

http://social.msdn.microsoft.com/Forums/is/xmlandnetfx/thread/d0aeb5a0-481e-4b5a-a82a-acc4b8be5986

http://professionalaspnet.com/blogs/aspnet_blog/archive/2006/04/07/A_name_was_started_with_an_invalid_character_Error_processing_resource.aspx

It helped me to install.

I hope it will be helpful to others too. :)

Thanks!

With best Regards

 

 

Jun 28, 2012 at 5:57 AM

is uninstalling Visual Studio 2010 and using 2008 version instead a solution to installation of sageframe in xp? if yes then how come I am using sageframe in vs 2010 using windows xp? if error is occuring due to VS 2010 the i wouldnt have had the sageframe installed. please check your service pack or iis settings it does work. hopefully this can resolve the issue without uninstalling VS 2010

if you are using xp then go to the location using command prompt

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\

Look for a file aspnet_regiis.exe

Execute the following command

aspnet_regiis.exe-i

After that execute this one

aspnet_regiis.exe-e

restart the server and check .

 

Thanks,

Fatimah Ali

Jun 29, 2012 at 5:42 AM
Edited Jul 1, 2012 at 11:20 AM

Hello Fatimah,

Thank you for the comment.


Jun 29, 2012 at 11:04 AM

uninstalling vs 2010 and installing vs 2008 is definitely not the solution. Like @fatimah82 said, the error occurs when you install IIS after installing dot net framework. In such cases it requires u to manually register the framework to the IIS using the aspnet_regiis.exe-i.

In ur case when u uninstalled vs 2010 and installed vs 2008, the dot net framework was reinstalled too, but this time it got registered to IIS, so it worked fine. Had you installed vs 2010 again, it would work like a charm.

But still running aspnet_regiis.exe -i is the best approach

Thanks.


Jun 29, 2012 at 12:10 PM
Edited Jun 29, 2012 at 12:23 PM

Hi Support,

I have successfully Installed AspxCommerce in my local System bt facing one problem related to currency type.. please tell me how can change currency type??

Thanks in Advance..

--

Abhay Jha

Jun 30, 2012 at 3:57 PM

Hello Abhay,

Changing currency type will only be available in the Paid version of AspxCommerce but if you require any customization  help then you can contact the support for that.

 

Thanks!

Jul 1, 2012 at 4:53 AM
Edited Jul 1, 2012 at 4:56 AM

Dear Abhay,

Thank you for using AspxCommerce and updating us about the AspxCommerce. We have sent you currency conversion script in your email with the required steps. Please follow up your email.

If you face any problem or want to ask any query regarding AspxCommerce, you can write to us at support@aspxcommerce.com .

Any Feedback(s) and suggestion(s) would be highly appreciated.

Thank you!

Regards,

AspxCommerce Support

Jul 1, 2012 at 7:56 AM

its working faultlessly on my pc with xp sp3 with vs2010 & laptop with windows 7 too. check your iis configurations properly uninstallation is not a true solution. sageframe users might get disgraced if they have similar system configurations.

Jul 1, 2012 at 8:24 AM
Edited Jul 1, 2012 at 11:25 AM

Hello spunkgeek,

Seems I have used SageFrame For .NET 3.5 now I am using http://sageframe.codeplex.com/downloads/get/364022 for .NET 4.0. It working perfectly.

Thank you very much for the Help.

Regards,

Renu Maharjan

Jul 1, 2012 at 9:42 AM

DuHHH - terrible !