Dave's Technophorical Times

A blog about Microsoft's Technologies!
SharePoint :: MVC :: ASP.NET :: IIS :: SQL Server :: Visual Studio :: MS Access

From here: https://blogs.msdn.microsoft.com/korbyp/2003/12/17/how-to-remove-a-project-from-source-control-in-visual-studio/

To (permanently) remove a project or solution from source control

1.      In Visual Studio, click File, click Source Control, and then click Change Source Control.

2.      In the Change Source Control dialog box, select the project and/or solution you want to remove from source control, and then click Unbind.

3.   Delete all solution or project files in the source control database.

4.      In Windows Explorer, locate the working directory for your solution/project and then delete all *.scc files.


Note   In Visual SourceSafe and many other SCC systems, if other users have checked out the solution/project in the past, even if they have since checked in their changes, the next time they attempt to Get or Check Out the solution/project, they will be prompted to add the items to source control from their working copies on disk. On the SourceSafe team, we call this a “pending add“, which is a little confusing. Anyway, if you want to guarantee that a solution/project is permanently, permanently, permanently removed from source control and will never again re-appear in your database, you should repeat the final step in the preceding procedure for all solution/project enlistees.



When you’re trying to open your SSIS or SSRS solution, you will get a message that the migration has failed or ‘The application which this project type is based on was not found.

From https://www.jonashendrickx.com/2017/06/26/cannot-open-ssrsssis-projects-vs2017/ 

Method 1

  1. Open ‘Microsoft Visual Studio 2017‘.
  2. In the menu bar, expand ‘Tools‘, then choose ‘Extensions & Updates‘. to install an extension.
  3. Search for ‘Microsoft Reporting Services Projects‘, and install this extension.
  4. To complete the installation, shut down all windows and instances of Microsoft Visual Studio 2017. Then the installer will start.
  5. Try to open your solution or projects (*.rptproj) again.

Method 2

  1. Close all windows and instances of ‘Microsoft Visual Studio 2017‘.
  2. Download ‘Microsoft Reporting Services Projects‘ from the Visual Studio marketplace.
  3. Open your solution or project.


7

The issue is, only adding nugget would not suffice. You need to install slowcheetah from visual studio marketplace. Following are the steps:

  1. Install SlowCheetah from Tools > Extensions and Updates
  2. Restart VS, allowing for the VSIX installer to run
  3. Create new C# App (.NET Framework). (In my case, it started to work on existing app also.)
  4. Show ALL Files in Project and you will see the Transformations

You will then also see the Transformation files in the Project file as explained below.

Unload the project and then Edit the project. Find the ItemGroup element that contains your newly created config file and add the <DependentUpon>Web.config</DependentUpon> element there, like so:



To "Dynamically" change the path of a Reference in Visual Studio you first need to Unload the Project, then Edit the *proj file.

Go down to the References Section change the Hard Coded Path to $(Configuration). This will dynamically change the reference when the Configuration is changed.

    <Reference Include="Dafran.Exceptions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=08f619978b79cd15, processorArchitecture=MSIL">

      <SpecificVersion>False</SpecificVersion>

      <HintPath>\\zero\Builds\Dafran.Security\$(Configuration)\Dafran.Exceptions.dll</HintPath>

    </Reference>



https://pureinfotech.com/set-gpu-app- windows-10/

https://www.techadvisor.co.uk/how-to/pc-components/how-set-default-graphics-card-3612668



Found Here: https://www.vspbreda.nl/nl/server-os/server-2012-essentials-users-dont-show-in-essentials-dashboard-after-migration-solved/ 

Issue. You add a User to AD but it does not show up in the Logon list in the Dashboard

Solution: Run PowerShell as Admin and run this command. Import-WssUser –SamAccountName “username”



  1. Dim cn As New ADODB.Connection
  2. Dim rs As ADODB.Recordset
  3. Dim strSQL As String
  4.  
  5. strSQL = "Select * from Employees ORDER BY [LastName],[FirstName];"
  6.  
  7. Set rs = New ADODB.Recordset
  8.  
  9. With rs
  10.   .Source = strSQL
  11.   .ActiveConnection = CurrentProject.Connection
  12.   .CursorType = adOpenDynamic
  13.   .LockType = adLockOptimistic
  14.     .Open
  15.  
  16.    Do While Not .EOF
  17.      Debug.Print UCase$(![LastName]) & ", " & ![FirstName]
  18.        .MoveNext
  19.    Loop
  20. End With
  21.  
  22. rs.Close
  23. Set rs = Nothing

 



You SHOULD replace the Nz with an IIf(IsNull()) construct as it's prone to Errors for NOT reason.

See documentation for IIf and IsNull

When put together:Nz(expr, [valueifnull])
becomesIIf(IsNull(expr), valueifnull, valueifnotnull)

Examples
Default: Nz(tbl.A) => IIf(IsNull(tbl.A), '', tbl.A)
With fallback: Nz(tbl.A, tbl.B) => IIf(IsNull(tbl.A), tbl.B, tbl.A)



These are som items that need to be considered/done when upgrading from MS Access backend to SQL Server backend.

1. Replace # with single quote (') for Dates in SQL.
2. Add Timestamp to all SQL tables.
3. Add dbSeeChanges to all DAO CurrentDB.Execute SQL statements. dbFailOnError should become dbSeeChanges + dbFailOnError
4. Convert all MulitValue fields to flat fields. This usually like multi-select combo baoxes that have to be converted to Listboxes.
5. Convert all Attachment Fields to VarBinary subTables!



OK here is how to un-associate a file extension to unknown . . . Right click your Desktop, choose 'New' - Text Document When the document opens, you need to save the document with a .bat file extension Click File - Save As At the bottom of the save as dialog, change 'Save as Type' to 'All Files' Manually enter the file name XXX.bat Now right click any file you want to disassociate and choose 'Open with' - 'Choose another app' -' More Apps' Check the box marked 'Always use this app' Scroll to the bottom and click 'Look for another app on this PC' Navigate to the XXX.bat on your Desktop and select that Finally delete XXX.bat from your Desktop and restart your system The file association will be reset to unknown . . .



The Blogger

Dave Stuart I'm a Developer with a passion for coding. I enjoy the challengers that come with the job! SharePoint is one of my expert areas along with .NET Web Development with MVC and good old MS Access VBA coding. I Blog so that I can remember how I did that way back when; PLUS all this stuff is searchable! I constantly study and run my own business, Dafran Inc. I have passed 22 Microsoft Exams since 1998 when I first jumped on the treadmill of knowledge. I hope that you enjoy this Blog as much as I enjoy updating it. All the very best from Calgary, Alberta, Canada. contact me at linkedin @ dafran.ca

Calendar

<<  April 2020  >>
MoTuWeThFrSaSu
303112345
6789101112
13141516171819
20212223242526
27282930123
45678910

View posts in large calendar

Sign in