Comments on: ASPX Edit Add-In For Visual Studio 2010

By: Rowland

Rowland — Wed, 30 Jun 2010 21:44:14 +0000

Thanks Ron.

The ID focus feature was dropped as:

- Getting it working was taking a lot of (unproductive) time
- I felt that it was better to release something that was 95% working rather than nothing at all

The editor in VS2010 is vastly different in behavior to 2008, particularly the way in which start and end positions of text are indentified and then selected.

It’s unlikely that I’ll get around to fixing this due to an ever increasing list of client work obligations.

The source code is available if someone would like to have a crack at it:)

By: Ron

Ron — Wed, 30 Jun 2010 20:10:55 +0000

Great that this functionality is back in VS 2010.
Unfortunately it does not work the same way as in 2008, at least on my machine.
Typing

BTW: By default VS 2010 does already include part of the functionality.
Unfortunately the default expand mechanism does NOT generate an ID at all.. Is this a bug?

Thanks

By: Jacob O.

Jacob O. — Fri, 07 May 2010 10:40:19 +0000

You are right; that solved my problem. Thank you.

By: admin

admin — Fri, 07 May 2010 09:08:39 +0000

This is probably due to some of the files being marked as having come from an untrusted zone (i.e. zip file). You can unblock the files using the property menu in explorer.

By: Jacob O.

Jacob O. — Fri, 07 May 2010 08:52:29 +0000

When I copy the three files ( AspxEditHelper.AddIn, AspxEditHelper.dll, AspxEditHelperSnippets.xml) to Documents/Visual Studio 2010/Addins folder I get an error on startup. Error: The Add-in ‘ASPX Edit Helper (VS 2010) – v1.0.0.2′ …failed to load or caused an exception…Error Message: Error number: 80131515.

I’m working with version 10.0.30319.1 RTMRel.

Thank you

By: Jacob Buus

Jacob Buus — Fri, 23 Apr 2010 17:38:02 +0000

Thank you very much Rowland! It works like a charm now without any popup messags.

You’re the greatest!

By: Rowland

Rowland — Thu, 22 Apr 2010 08:12:34 +0000

**Version 1.0.0.2 RELEASED**

NOTES
Some users were reporting spurious popup error messages. I’ve not been able to reproduce these errors here but have added one code fix for potential null reference exceptions produced at End Of Line (EOL).

These are now 2 binary builds.

“Release”:
This has all exception / error popups supressed. This is the version that you should install initially.

“Debug”:
If the add-in is not working for you, please install this version as it has all debug popups / messages enabled. It would be really helpful if you could post the messages that you see on this page so that I can identify and fix your problems:)

When I took this on, I didn’t realize how much Microsoft had changed the way that the editor works in VS2010. These changes are why Dereks original add-in stopped working and why it’s taking some time to iron out the bugs in my port.

Thanks for the feedback so far. Keep it coming!

By: Jacob Buus

Jacob Buus — Wed, 21 Apr 2010 16:25:25 +0000

Thank you very much! It would be great if you could just silence the error code as it doesn’t seem to do anything of much importance.

Thank you so much for this!

By: Rowland

Rowland — Wed, 21 Apr 2010 15:48:45 +0000

Ok Jacob,

Hmm..

Trying hard (15 minutes bashing keyboard in ASPX file) to re-create the problem here but no luck.

I’m looking at the source now and there is only one place it could create the error message you describe.

As I’m not able to re-create the error here it makes it difficult to fault-find. Therfore, I’m thinking of knocking out the error notifications completely and let it fail silently..Here comes 1.0.0.2;) Give me a day or so to recompile & upload.

By: Jacob Buus

Jacob Buus — Wed, 21 Apr 2010 15:22:47 +0000

The 1.0.0.1 is the only version I’ve tried – and I’m sorry to say it’s not quite working for me