FoxPRO Commands in Dreamweaver - adobe

does any of you know how to use this FoxPRO command "<%= and %>" in Dreamweaver?
coding gets trash with these commands <%= and %>

Related

How to enable Intellisense for Classic ASP in Visual Studio 2015?

Is there any way to get Intellisense for classic ASP for Visual Studio 2015, and still have html and JavaScript formatting/Intellisense? I tried adding an extension and using html forms but it seems to not detect <% and %> tags.

<%#: %> working locally but causes "Expression expected" on server

This is not a duplicate of the above linked question - I'm fully aware of the difference between the two code blocks, just read the first line of the question!
(This will only make sense if the "This question may already have an answer here:" is still showing above)
I have recently discovered the <%: %> inline code block (to automatically Server.HtmlEncode the output), as well as the data binding version of <%#: %>.
I have a <asp:Repeater> which contains several <%#: %> blocks which is working locally on my development machine, but causes the following error when published to the server.
BC30201: Expression expected.
The code works correctly if I convert all instances of <%#:...%> to <%#Server.HtmlEncode(...)%>
Using <%: %> in the code on the server, does work.
The application pool in IIS (both my local machine and the server) is setup to use .NET4.0.
Is there anything obvious that could cause the error to happen on the server?
UPDATE
Thanks to #vcsjones, they have correctly pointed out that I have .Net 4.5 installed on my local machine (which I was positive was not the case).
This is the link they helpfully provided to see this was case.
This is because ASP.NET 4.5 was installed locally, and not on the server. The <%#: binding syntax was introduced in ASP.NET 4.5. The <%: and <%# syntaxes existed before 4.5, so that's why they work remotely as well.
The .NET Framework 4.5 is a "drop in" replacement for 4.0, so even if your project specifically targets .NET 4.0, it will still use the 4.5 parser if it's installed, which was happening locally.

Debugging VB code in aspx files

I am converting an old asp project to a new .NET project. Now, all vb code are inside aspx files, and we are on the process of moving all vb script from aspx files to .vb files. My problem is, I can't debug the vb script inside most of the aspx files. All my friends don't have this problem. I think the problem is with vb text editor.
I am using Visual Studio 2008.
Is there anyway, I can make visual studio understand that aspx files have vb script inside them.
can't debug the code
can debug the code
You can set a breakpoint on a particular line in the VB Script. If that line is hit you will see Visual Studio highlight that line.
You can use the Visual Studio Debugger to debug a .vbs (vbscript) file executed with cScript.exe by using the //X flag at the command line. To debug MyTest.vbs
cscript.exe MyTest.vbs //X
The //X will set a breakpoint and invoke the "select a debugger" dialog where you can choose Visual Studio and step into your vbs code.

classic asp syntax highliting inside javascript in Visual web developer ee 2008

How can visual web developer Express Edition highlight the classic asp-Tags (<% asp code %>) insight the Javascript code?
If i write
<script>
alert("<% =session("user_name %> ");
</script>
VWD highlights this as a string and not as asp-code. This is total confusing in these old files i'm working with.
Looks like this is a known issue on Microsoft Connect with a few workarounds, however the syntax highlighting was removed in VS2008. The response from Microsoft (verbatim):
Thank you for this feedback. We are
depcrecting VB Script colorization and
intellisense support in Visual Studio
2008. We recommend to customers to use VS 2005 or VWD 2005 to edit VB
Script.
Those products can be installed on the
same machine as VS 2008 without any
issues.
Visual Web Developer Team
Check here for more information:
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=290845

Is intellisense not working properly in VS 2008?

I've got trouble getting Intellisense to work in ASP.NET source view.
For example, I register the Telerik RadControls DLL with a tag prefix, as it says in the samples:
<%# Register Assembly="Telerik.Web.UI" Namespace="Telerik.Web.UI" TagPrefix="telerik" %>
But when typing <telerik: no intellisense appears.
Also, after adding a couple of controls, they get highlighted with the error "Unrecognized tag prefix or device filter 'telerik'". This is pretty annoying and I can't seem to find a solution.
Btw, the webpage itself works - its just the Intellisense that doesn't.
Intellisense may fail for various reasons so I am going to ask you a few questions:
Does design time work as expected?Sometimes if the design-time assembly is not loaded intellisense may fail.
Do you work on a remote drive by any chance? We have found issues with that as well. The remote drive needs to be added as a trusted location for assemblies.
If you are using an older version of RadControls you need to add reference to Telerik.Charting.dll as well. Which version do you use?
Finally we have found that upgrading to Visual Studio 2008 SP1 solves lots of problems. I strongly recommend you upgrade if not already.
Does your entire project compile? Intellisense often breaks if there are compile errors elsewhere (even compile errors in other pages).
ctrl + space is a shortcut to trigger it ...
probably won't help but at least you will know that the problem is probably with intellisense not being able to find its data.
do you get intellisense for other classes still?
I noticed a general problem with intellisense in VS2008 (with SP1).
As they started supporting JS intellisense a lot of things became slower - or not working sometimes.
I know the describe problem - not only with telerik controls, I also know it from other (and my own) control libraries.
Most of the time a rebuild - close of all pages, and restart of VS solves the problems for me.
My special problem (I guess it matters) is that I use a German release of VS2008.
But also other things rule (from my experiences):
The size of the project (somewhere above 50 pages things become worse).
The time I had to kill an app while debuging :)
General the time (in a session) I work on a project.
A last tip (which may help) I feel less problems when I add a ref to the controls directly in web.config. Additionally it frees me from havin the register directive on every page.
It looks like this:
<controls>
<add assembly="Telerik.Web.UI" namespace="Telerik.Web.UI" tagPrefix="telerik" />
<add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions,
HTH
Manfred
Just fixed this myself for VS2008 (for aspx/ascx and codebehind) by adding the Telerik .dlls to the GAC on my local development machine.
I've had this issue before and both times it occurred was when my project was hosted on a network drive, where the project's path would be something like: *\\networkmachinename\c$\inetpub\projectname*
The fix:
On your local machine, go to Start > Programs > Microsoft Visual Studio 2008 > Visual Studio Tools > Visual Studio 2008 Command Prompt (run as admin)
Using the gacutil tool and the following commands (or more depending on how many .dlls you wish to use), add the assemblies to your GAC:
gacutil.exe -i "C:\Program Files (x86)\Telerik\RadControls for ASPNET AJAX Q2 2008\Bin35\Telerik.Web.UI.dll"
gacutil.exe -i "C:\Program Files (x86)\Telerik\RadControls for ASPNET AJAX Q2 2008\Bin35\Telerik.Charting.dll"
Obviously modify the dirs as appropriate for your OS/Telerik/Framework versions, then close Visual Studio 2008 Command Prompt, close VS2008 (if open) and restart VS2008 again.
You'll find the intellisense works on the aspx/ascx files first, and given a few minutes it'll work on your codebehind files too. Close and retry if it still doesn't work.
One other note, if you have a small error somewhere in your website's root web.config file, you'll also lose intellisense for Telerik (and perhaps other) controls - so check your web.config files aren't erroneous first.

Resources