3 ms·

> I'm using a Web Site + solution for my current job though, know if it handles that? To be honest I'm not really sure. The big test would be to see if Zeus ma

by jussij 16y ago

> I'm using a Web Site + solution for my current job though, know if it handles that? To be honest I'm not really sure. The big test would be to see if Zeus manages to import the solution file (i.e. from the Workpsace, Import menu). This import has only been tested for 2005, 2008 and 2010 C# and C++ projects. If it doesn't feel free to send me a bug report. > I'll certainly give it a try for more "normal" .NET coding, there's a lot of utility code to be written :) These are the three 'one off' steps needed to get the Visual Studio compiler to run inside Zeus http://www.zeusedit.com/zforum/viewtopic.php?t=2707 http://www.zeusedit.com/zforum/viewtopic.php?t=2707

Groxx 16y ago
Tried it a little bit, and I'll experiment more as I get time. Importing the solution which contained the web site only loaded the other "actual" project in the solution, unfortunately. I can poke at it a bit more and see if I can get more into it. One of the first things I noticed: apparently a couple of your regexes are off in C#, for VS2008 at least. Typed interfaces come up as "T" instead of the interface, and it would be immensely more useful to have the class browser have information about the parameters of functions. I've got a ton of overloads, and they're note even in any useful order, as far as I can tell.
- jussij 16y ago
  > Importing the solution which contained the web site only loaded the other "actual" project in the solution, unfortunately. That is what I had feared. It looks like Zeus will need to be tweaked to understand this type of solution file. > I can poke at it a bit more and see if I can get more into it. One thing you could try is opening an explorer window and then just drag and drop one of your source code folders onto the Zeus workspace panel. Zeus will parse the structure of the folder that was dropped and add all files that if finds to the project/workspace. > One of the first things I noticed: apparently a couple of your regexes are off in C#, for VS2008 at least. The use of a regexp to identify functions is a Zeus feature that dates back to one of the very early versions and is no longer the primary method of identifying functions. What should have happened is for Zeus to create a tags database for all the files in the project/workspace and it then uses that tags information to display the function list. But in this case since the solution was not imported correctly, the workspace is empty of files. As such Zeus reverted back to the older regep approach to identify the functions. And as you suggest, the regexp that it used is almost certain to be out of date since, it was probably written even before the time of C#. > it would be immensely more useful to have the class browser have information about the parameters of functions. Adding the current file (or all the project files) to the workspace should result in a lot more information being seen in the class browser. The class browser shows the contents of the tags database and if it is not full then it means the tagger is not understanding the code, but for C# that should not be the case.

by jussij 16y ago

Groxx 16y ago

Tried it a little bit, and I'll experiment more as I get time. Importing the solution which contained the web site only loaded the other "actual" project in the solution, unfortunately. I can poke at it a bit more and see if I can get more into it. One of the first things I noticed: apparently a couple of your regexes are off in C#, for VS2008 at least. Typed interfaces come up as "T" instead of the interface, and it would be immensely more useful to have the class browser have information about the parameters of functions. I've got a ton of overloads, and they're note even in any useful order, as far as I can tell.

jussij 16y ago
> Importing the solution which contained the web site only loaded the other "actual" project in the solution, unfortunately. That is what I had feared. It looks like Zeus will need to be tweaked to understand this type of solution file. > I can poke at it a bit more and see if I can get more into it. One thing you could try is opening an explorer window and then just drag and drop one of your source code folders onto the Zeus workspace panel. Zeus will parse the structure of the folder that was dropped and add all files that if finds to the project/workspace. > One of the first things I noticed: apparently a couple of your regexes are off in C#, for VS2008 at least. The use of a regexp to identify functions is a Zeus feature that dates back to one of the very early versions and is no longer the primary method of identifying functions. What should have happened is for Zeus to create a tags database for all the files in the project/workspace and it then uses that tags information to display the function list. But in this case since the solution was not imported correctly, the workspace is empty of files. As such Zeus reverted back to the older regep approach to identify the functions. And as you suggest, the regexp that it used is almost certain to be out of date since, it was probably written even before the time of C#. > it would be immensely more useful to have the class browser have information about the parameters of functions. Adding the current file (or all the project files) to the workspace should result in a lot more information being seen in the class browser. The class browser shows the contents of the tags database and if it is not full then it means the tagger is not understanding the code, but for C# that should not be the case.