471,320 Members | 2,074 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,320 software developers and data experts.

visual studio does not handle user control ascx files - web matrix does!

what a waste of money.

visual studio does not handle user control files - these are files with
and ascx extension are are refered to in the help as 'user-authored
server controls'.

the VS help says to use a text editor to create these controls (i
wonder if they'd recommend emacs) - however, web matrix handles these
files fine and you can use the designer to alter them.

the only way i think i can kludge around it is to create aspx files and
then (using an editor) manually convert them to ascx files.

but after paying out a small fortune on this VS thing we should not
have to kludge around anything.

as these files are developed there may be changes - so - find original
aspx file - edit file - remove stuff and add references (manually) to
convert - rename with ascx extension - overwrite existing ascx file.

not a simple kludge and why should i even have to consider this?

having something in web matrix but not in VS is completely unexpected -
and now you have a very disgruntled client who is getting more
disgruntled with MS every day.

Aug 4 '05 #1
1 1983
Works fine here in VS.NET 2003... Which version are you using ?

Give it also a try by yourself in case the doc would be out of sync with the
product...

--
Patrice

<kb*****@freewayprojects.com> a écrit dans le message de
news:11**********************@g47g2000cwa.googlegr oups.com...
what a waste of money.

visual studio does not handle user control files - these are files with
and ascx extension are are refered to in the help as 'user-authored
server controls'.

the VS help says to use a text editor to create these controls (i
wonder if they'd recommend emacs) - however, web matrix handles these
files fine and you can use the designer to alter them.

the only way i think i can kludge around it is to create aspx files and
then (using an editor) manually convert them to ascx files.

but after paying out a small fortune on this VS thing we should not
have to kludge around anything.

as these files are developed there may be changes - so - find original
aspx file - edit file - remove stuff and add references (manually) to
convert - rename with ascx extension - overwrite existing ascx file.

not a simple kludge and why should i even have to consider this?

having something in web matrix but not in VS is completely unexpected -
and now you have a very disgruntled client who is getting more
disgruntled with MS every day.

Aug 4 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by mivhaelveloz | last post: by
reply views Thread by rosydwin | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.