SPVisualDev - SharePoint Developer Tool

Closed Issue: Feature event receiver is not removed when unchecking the checkbox in feature settings. [104]

tore7506 — Thu, 16 May 2013 05:08:41 GMT

Feature event receiver is not removed when unchecking the checkbox in feature settings. This is because SPVisualDev doesn't remove any existing code files automatically. When the settings dialog is closed and saved it will automatically refresh the feature definition and find that the event receiver code still exists.

Workaround:
Delete any existing code files which is referenced by the event receiver declaration in the feature definition before unchecking the box in feature settings. You can remove the assembly and class attributes from the feature definition as well.

Issue status:
Evaluate whether this function should be revised or removed in future releases.

Closed Issue: Feature settings wizard [157]

tore7506 — Thu, 16 May 2013 05:08:41 GMT

When clicking on wizard button when selecting a content type element it reverts some values back to the xml definition for that element. Any changes made in the property grid will not be saved.

Closed Issue: Files synchronization inside modules is not working properly [1756]

tore7506 — Thu, 16 May 2013 05:08:41 GMT

Files inside module definitions are added to the last elements file although they already exist in other element definition.

Closed Issue: TargetInvocationException [2369]

tore7506 — Thu, 16 May 2013 05:08:41 GMT

Sometimes, SPVisualDev fails and throws a TargetInvocationException when we try to do any feature actions.

Cause: If any of the app pool is turned off, this happens.

Solution: Either turn on or delete that app pool

Closed Issue: Error when installing 1.6.3 on windows 2003 server [2555]

tore7506 — Thu, 16 May 2013 05:08:40 GMT

An error has been reported when installing version 1.6.3 on windows server 2003.

Closed Issue: Folder names in 12 hive (features for example) cannot be spelled with capital letters [2967]

tore7506 — Thu, 16 May 2013 05:08:40 GMT

I have discovered that in version 2 you have to name your folders in the 12 hive according to what SPVisualDev thinks. For instance, if I name the Features folder FEATURES the tool won´t recognize it as the features folder.
Oh, this is probably only when I apply the tool on a project that was not created with the tool to start off with.

Closed Issue: Error deactivating features from context menu [2990]

tore7506 — Thu, 16 May 2013 05:08:39 GMT

Features can not be deactivated from the context menu. Instead the activating command is sent when deactivating should be sent.

Closed Issue: Error when saving artifact configuration [3009]

tore7506 — Thu, 16 May 2013 05:08:39 GMT

An error message is popping up when saving artifact configuration on project.

Closed Issue: Rebuild SPVisualDev source code is missing reference to Microsoft.VisualStudio.Web.Application [3010]

tore7506 — Thu, 16 May 2013 05:08:39 GMT

When i rebuild solution i have this error: The type or namespace name 'Web' does not exist in the namespace 'Microsoft.VisualStudio' (are you missing an assembly reference?).

I don't found the Microsoft.VisualStudio.Web.... assembly

Closed Issue: Error when opening files in Visual Studio when not in a solution [3067]

tore7506 — Thu, 16 May 2013 05:08:39 GMT

An error message may appear if you open files in Visual Studio which has no solution loaded.

Fix is on its way..

Closed Issue: SPVisualDev info files (.spvdinfo) on non SPVsualDev solutions [3068]

tore7506 — Thu, 16 May 2013 05:08:38 GMT

An info file is created on solution that has no SPVisualDev enabled projects. It is placed in the same directory as the solution file.

Closed Issue: Attached event receivers classes problem in an unbuild project [3071]

tore7506 — Thu, 16 May 2013 05:08:38 GMT

When attaching event receiver classes to a list template element for example, it won't register them unless the project has been built once.

Workaround: Build project and reassign them again in the feature editor (feature settings) then it will work.

Fix is on its way...

Closed Issue: File and directory permissions in 12 hive causes problems [3078]

tore7506 — Thu, 16 May 2013 05:08:38 GMT

File permissions are not inherited when pushed down to 12 hive which can cause problems in some scenarios. If file access problems appears in SharePoint or when files are pushed down, reset the permissions on those directories / files manually until fix is available. Thanks Ryan for reporting this problem!

Closed Issue: Error when adding ListItemEventReceiver from dialogue [3172]

tore7506 — Thu, 16 May 2013 05:08:37 GMT

When adding ListItemEventReceiver code from the UI (as a sideissue it is a little strange that I have to click on the featureeventreceiver ... button to add the .cs file for listitemeventreceiver) SPVisualDev throws an error which says that the class have to inherit from SPFeatureReceiver but when I click OK it still has added the correct file and the correct featurereceiver is still shown in the xml (as it should be). Could you have a look at this?

Closed Issue: Problem (bug?) in building wsp and temp. workaroud [3216]

tore7506 — Thu, 16 May 2013 05:08:37 GMT

Hi,

I'm writting this quick notice on a bug/issue I had experienced while working with SPVisualDev.

Basicaly the problem is this: on selecting the build wsp option I get an error stating that some file in the project is locked.

From what I have gathered so far the cause of this anomaly is found in the fact that SPVisualDev in the background creates a working folder for building the wsp and then copies there the required dlls (the ones selected for adding in the wsp - artifact configuration). The "problem" is that in my case some of those dlls are begin included in the project as files (think of a folder "dll/someLibrary.dll", something like what spvisualdev creates with the "remotely add sharepoint dlls" feature), and that files are under source control and checked-in... I can only guess that when the files are copied they copy the read only attribute.. and so spvisualdev will crash when performing cleanup of the folder. What I know for sure is that if you start with a clean wsp folder and checked out referenced dlls the problem seems to dissappear.

I know that this might sound unclear - I haven't had any time to look at the sourcecode, so I could post only a guess of what I THINK could be wrong. I will try to see if I can discover something more accurate when I get some time - for now I hope that this notice can help other dev out there with the same problem - if you get an error that says "file xyz could not be accessed" (or something similar) while building the wsp try this two step:

delete the wsp folder (make a backup copy if you think you may need the contents)
check out the file.

PS: please tell me if I should create a issue report... I have posted here only because I don't have many info on what is the real cause of the problem (as I said, I can only guess that it is the read only attribute that gets copied on the file in the working folder).

Closed Issue: Error when ListInstance Id attribute is other type than an integer [3222]

tore7506 — Thu, 16 May 2013 05:08:37 GMT

Feature settings dialog will crash if the ListInstance Id is not an integer. Although msdn documentation states it should be an integer people often use a GUID or other text instead. The fix is to change the code so it accepts any types and treat the attribute as text instead.

Closed Issue: Errors occur when creating a new project. [3327]

tore7506 — Thu, 16 May 2013 05:08:36 GMT

Hi there,

I've heard great things about this software, but am having trouble getting it started OOTB

Steps I've taken.

1. Installed the latest download and ran setup.exe on server 2003; Visual Studio 2008.
2. Installation reports success.
3. Open a new VisualDevProject
4. Receive the following error dialog "Failed to initialize solution. The path is not of a legal form" (attached screen shot).
5. Dialog reports that the project has been created successfully.
6. A dialog appears with the error message "Object reference not set to an instance of an object."

Having opened the solution any attempt to right click the project and select SPVisualDev->Artefact.config receives the error message from 6.

If you could shed some light or provide a work around I would be most grateful as I'm truly very eager to give this software a whirl.

Cheers,

Ben.

Closed Issue: Error msg: "SharePoint farm could not be found. Check the service log on account..." [3501]

tore7506 — Thu, 16 May 2013 05:08:36 GMT

An error containing the message "SharePoint farm could not be found. Check the service log on account and make sure it has access to the SharePoint config db." is displayed on certain operations for example when building, recycling application pools etc.

SPVisualDev doesn't seem to correctly determine whether it is a 64 bit SharePoint installation or not. Will be fixed in the next version.

Closed Issue: Settings error when creating new project [3552]

tore7506 — Thu, 16 May 2013 05:08:35 GMT

Hello!

First off, great job! Keep up the good work.

I just downloaded 2.1.3. I had no previous version installed, and I'm running VS2008 SP1.

I jumped at the gun and created a new SPVisualDev project (no solution created). The project gets succesfully created, but when I'm redirected to the settings part of the process an exception is thrown. The same exception is also thrown when I right click and chose Artifact config. I've attached the error message as an image in this post.

However, after I save the project and open it again the exception is not thrown anymore and I can change the Artifact config.

Hope this is of help.

Best regards!

Closed Issue: [Bug?] Possible issue with receiver class. [3561]

tore7506 — Thu, 16 May 2013 05:08:35 GMT

Hi,

I'm writting this notice to report a (possible) issue that I have experience while working with SPVisualDev. I dont't know if it should be considered a bug, a limit of the current version or simply a false issue caused by a missunderstaning of the configuration settings of the artifact project.

Basically the problem is this: under certain circumstance, SPVisualDev triggers a strange behaviour while working with feature.xml files and feature receiver and automatically updates the current setting with incorrect data. I work on a solution where the feature receiver classes are placed in a different project than the artifac project: every time i install a feature with an event receiver from the ide (but i saw the same issue happening on a wsp build) SPVisualDev tries to update the feaute.xml file and replaces the ReceiverClass and ReceiverAssembly setting with some "random" namespaces (seems to be the namespace used by the artifact project).No need to say that this anomaly leed to problems when you try to activate the feature form SharePoint (a nice "Failure creatin the feature reciver object" if I recall well)...

The funny part is that if you have the luck to work source controlled you can simply workaround the problem by dismissing the file checkout prompt on the feature.xml file - the setting will remain untouched and all will work as expected.

I'm writting this here (and not in the issue section) because I dont know if this issue while dangerous could be considered a bug or it is a limit of the current version, so i'm hoping to bring some light - maybee someone else has experienced this? It would be usefull if Tore could also confirm if having a feature receiver class ina a different project is supported (or if we should configure something with the default feature namespaces??) - just to know if it 's worty to make some other test or it's better to leave this issue alone for now.

Thanks again for your tool - will try to see if i discover something else and report here any new discovery.